@0xlr/vercel-analyticsnpm
Malicious code in @0xlr/vercel-analytics (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
On npm install, postinstall.js enumerates every process.env variable (including credentials such as AWS_*, NPM_TOKEN, GITHUB_TOKEN and other CI tokens) and collects host fingerprint data — hostname, username, homedir, cwd, argv, and platform — then POSTs the JSON payload to https://rytxau88zxh61dw6qz4yn19naeg54vsk.oastify.com/. The destination is a Burp Suite Collaborator (oastify.com) out-of-band interaction host, used here as an attacker-controlled exfiltration sink. The package name @0xlr/vercel-analytics impersonates Vercel's @vercel/analytics, and the 999.0.0 version plus the self-described Placeholder reservation text are the canonical shape of a weaponized dependency-confusion squat designed to override an internal package of the same unscoped name.
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/vercel-analytics (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/vercel-analytics across your stack and pipelines.
If you installed it — respond
@0xlr/vercel-analytics 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/vercel-analytics 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/vercel-analytics 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/vercel-analytics-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.