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 (4f356f513bed48330cd1a0538e53ac429f5570385e8b0bcc3fcc5c94876e437b)
package.json declares its sole dependency `shard-writer-parser-mutex` as a bare HTTPS URL to a non-registry host (`https://artifacts.creditslib.com/npm/shard-writer-parser-mutex`) rather than a semver range against the npm registry. On `npm install`, npm fetches whatever tarball that URL currently returns and installs it, executing any lifecycle scripts it contains; the shipped `index.js` is a one-line re-export, so loading this package also loads code from that host. The URL is unpinned (no version, no commit, no integrity hash), the host is unrelated to the npm registry, and the content served there can change at any time without any republish of this package. The declared dependency name also mirrors the host package's own naming shape, consistent with a dependency-confusion lure where the manifest itself is the delivery mechanism.
Source: ghsa-malware (aa1723c1a5589a8e05f050b8315839ef0733a2429c6da7993fba409cd36188de)
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.