Which versions of next-simple-google-analytics are malicious?

The following npm versions of next-simple-google-analytics are flagged malicious: 1.1.1, 1.1.2. Treat any of these as compromised.

How do I remediate next-simple-google-analytics if I installed it?

next-simple-google-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.

I already installed next-simple-google-analytics — how do I know if it already compromised me?

If next-simple-google-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.

Is next-simple-google-analytics part of a known attack campaign?

Yes — next-simple-google-analytics is associated with the GHSA-4f6w-f258-xf3r 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 next-simple-google-analytics 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 next-simple-google-analytics (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging next-simple-google-analytics across your stack and pipelines.

Malicious package

next-simple-google-analyticsnpm

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

MAL-2025-190980

Immediate action

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

npm uninstall next-simple-google-analytics

What this malware does

The package next-simple-google-analytics 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

2 flagged

1.1.11.1.2

Indicators of compromise (SHA-256)

3ed32a3cc64dcafde415a3b1ed7940f39e817b943c19745ec4410e5c23280c23

65c0df29a06f4738e26d90f0418c197f39ad60e98981f43cff7baaa82a672ced

7e27d1569237affffda8b11d32b2d38e826cf70e0f1b0377364d810015bc8ff0

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 next-simple-google-analytics (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging next-simple-google-analytics across your stack and pipelines.
If you installed it — respond
next-simple-google-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 next-simple-google-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 next-simple-google-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

No. next-simple-google-analytics on npm has been identified as a malicious package (versions 1.1.1, 1.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4f6w-f258-xf3r

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks next-simple-google-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.

Malware detection Runtime egress monitoring