Which versions of @0xlr/vercel-analytics are malicious?

The following npm versions of @0xlr/vercel-analytics are flagged malicious: 999.0.0. Treat any of these as compromised.

How do I remediate @0xlr/vercel-analytics if I installed it?

Remove @0xlr/vercel-analytics from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is @0xlr/vercel-analytics part of a known attack campaign?

Yes — @0xlr/vercel-analytics is associated with the IN-MAL-2026-004974, IN-MAL-2026-004973 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect @0xlr/vercel-analytics in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking @0xlr/vercel-analytics and packages like it before any post-install script runs.

Malicious package

@0xlr/vercel-analyticsnpm

Malicious code in @0xlr/vercel-analytics (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5391

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @0xlr/vercel-analytics

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

1 flagged

999.0.0

Indicators of compromise (SHA-256)

7b1f5b447021e3782c516e27d02a751f714d885ebfd7fd9751de5921a42bac93

fda046018b2c121cb96e157cadce6d8aee695beb7086008140da0a9c6eebc938

Frequently asked questions

No. @0xlr/vercel-analytics on npm has been identified as a malicious package (version 999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004974IN-MAL-2026-004973

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection