Which versions of analytics-v2 are malicious?

The following npm versions of analytics-v2 are flagged malicious: 4.0.0. Treat any of these as compromised.

How do I remediate analytics-v2 if I installed it?

analytics-v2 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.

I already installed analytics-v2 — how do I know if it already compromised me?

If analytics-v2 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.

Is analytics-v2 part of a known attack campaign?

Yes — analytics-v2 is associated with the IN-MAL-2026-018751 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find analytics-v2 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for analytics-v2 (version 4.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging analytics-v2 across your stack and pipelines.

Malicious package

analytics-v2npm

analytics-v2 is a confirmed malicious npm package (MAL-2026-14531) that steals credentials and exfiltrates sensitive data (malicious version 4.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in analytics-v2 (npm)

MAL-2026-14531

Immediate action

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

npm uninstall analytics-v2

What this malware does

On npm install, the package's preinstall hook executes index.js which harvests host and user identity data (os.hostname(), os.platform(), os.arch(), os.userInfo() including username/uid/gid/shell, homedir, cwd) and captures the output of the shell commands whoami and id via child_process. The collected data is serialized as JSON and POSTed to the hardcoded endpoint https://839wbtybgrvpgbqzd0l8po2ozf56tyhn.oastify.com/system-info, a Burp Collaborator (oastify.com) out-of-band interaction subdomain unrelated to any legitimate analytics functionality. The behavior fires automatically as part of the npm install lifecycle with no user interaction.

Malicious versions

1 flagged

4.0.0

Indicators of compromise (SHA-256)

a589041eddd586d6269526f6c6e67f6b645994a24a143af07e35d8e2f9ce0982

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for analytics-v2 (version 4.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging analytics-v2 across your stack and pipelines.
If you installed it — respond
analytics-v2 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 analytics-v2 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 analytics-v2 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

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

Campaign

IN-MAL-2026-018751

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks analytics-v2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database