Which versions of analytics-browser are malicious?

Every published version of analytics-browser on npm is considered malicious. Remove the package entirely.

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

Remove analytics-browser 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 activity or persistence.

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

If analytics-browser 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-browser part of a known attack campaign?

Yes — analytics-browser is associated with the GHSA-67vh-wg5g-567j 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-browser 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-browser (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging analytics-browser across your stack and pipelines.

Malicious package

analytics-browsernpm

Malicious code in analytics-browser (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-214

Immediate action

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

npm uninstall analytics-browser

What this malware does

The package analytics-browser was found to contain malicious code.

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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

13a55b00a9f1b09ab75f1140b683d79dd9ede64c975cdf35bd8a71b3ce2781ae

d14b7ad7441a8663be12ffffb8132ef2a0b0124006d5df1b3448d6f722e4f808

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for analytics-browser (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging analytics-browser across your stack and pipelines.
If you installed it — respond
Remove analytics-browser 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 activity or persistence.
Did it already run?
If analytics-browser 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-browser 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-browser on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-67vh-wg5g-567j

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks analytics-browser-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring