@0xlr/stripe-frontendnpm
Malicious code in @0xlr/stripe-frontend (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @0xlr/stripe-frontend (version 999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @0xlr/stripe-frontend across your stack and pipelines.
If you installed it — respond
@0xlr/stripe-frontend is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @0xlr/stripe-frontend was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @0xlr/stripe-frontend before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @0xlr/stripe-frontend-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.