Malicious code in fnd-stores (npm)

-= Per source details. Do not edit below this line.=-

Source: amazon-inspector (62c9035e303ec731c71c689ed77eed17b245cd4adc475cb616ff94991539aa56)

On npm install, the package's postinstall hook runs node index.js, which collects the installer's hostname, OS platform, current working directory, CI environment indicators, Node version, and OS username via os.hostname(), os.platform(), os.userInfo(), process.cwd(), and process env, and POSTs the payload as JSON to https://webhook.site/604bab71-0179-419e-998e-6f15e524bfd7 (a publisher-controlled webhook bin). The README self-describes the package as a dependency-confusion canary targeting an internal package namespace, and the name is chosen to collide with that internal scope. Any developer or build pipeline that resolves this package leaks internal hostnames, usernames, working-directory paths, and CI job metadata to a third party at install time, without consent. Claimed 'authorized research' status does not change the installer-side harm.

Source: ghsa-malware (a5a8570b79443f0d67df3ba972632cad2ea7227e3be9907edaa1c6e9a140f166)

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.