If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (f28b41919d402aff87ec13d36b2419e4c19dcc209dcb6ffa3e736de5be2803e6)
package.json declares its sole runtime dependency `client-marker-packet-cluster` as an arbitrary HTTPS tarball URL on a non-registry host (`artifacts.stg.yosiroute.com`), and `index.js` unconditionally re-exports that dependency via `module.exports = require('client-marker-packet-cluster')`. Installing this package causes npm to fetch and load code from that host into the installer's dependency graph with no version pin, no integrity hash, and no publisher relationship to the declared repository. Whoever controls `artifacts.stg.yosiroute.com` controls the code that executes when a consumer of this package `require()`s it. Package metadata is placeholder-shape (author `Package Registry`, description `Generated package`, repository pointing to a non-existent `github.com/example/...` org), so no legitimate publisher context anchors the external code source.
Source: ghsa-malware (5cc5e745852cc2c791421f3bf384a281040b1cf8e01f8e74782b2a48fe0390b8)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.