@0xlr/stripe-frontend
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-c3gr-xj4c-rc53
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in @0xlr/stripe-frontend (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (3eda7bf8681a6253ffc4bc965888e45c5374e4ba8d4fe2e17efcd0f227d7ce5e)
On npm install, postinstall.js enumerates every entry in process.env (sorted), bundles it with hostname, username, homedir, cwd, argv, and platform/arch, and POSTs the JSON payload over HTTPS to the hardcoded Burp Collaborator subdomain rytxau88zxh61dw6qz4yn19naeg54vsk.oastify.com. Any tokens present in the install environment (AWS, GCP, CI tokens, npm tokens, etc.) are leaked to the attacker. The package's own metadata describes itself as a placeholder reservation for 'stripe-frontend' at version 999.0.0 under the @0xlr scope, indicating a namespace-squat against the Stripe brand whose only payload is the exfiltration script.
Source: ghsa-malware (bcb5a6da1d3d09334af2cf081d594084669d66e00080c553168acec966e70d96)
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.
Not rated by the source.
0 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0