Which versions of generator-meteor-stock are malicious?

The following npm versions of generator-meteor-stock are flagged malicious: 0.1.6. Treat any of these as compromised.

How do I remediate generator-meteor-stock if I installed it?

generator-meteor-stock 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 generator-meteor-stock — how do I know if it already compromised me?

If generator-meteor-stock 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 generator-meteor-stock part of a known attack campaign?

Yes — generator-meteor-stock is associated with the GHSA-f53h-6gfq-fcmj 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 generator-meteor-stock 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 generator-meteor-stock (version 0.1.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging generator-meteor-stock across your stack and pipelines.

Malicious package

generator-meteor-stocknpm

Malicious code in generator-meteor-stock (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191101

Immediate action

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

npm uninstall generator-meteor-stock

What this malware does

The package generator-meteor-stock 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

1 flagged

0.1.6

Indicators of compromise (SHA-256)

c93a2513bdfef16e59fd2849937429d9db6349f12e6de8c524d4db0c2ec492a4

25943e60bd7cad72187a4d899ee3d8117006f6ec12bd0415ac668cb896aed34a

678199611d26a80c99b9cad377ac570dda69e8bc8ed1114a1178d98c2c611973

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 generator-meteor-stock (version 0.1.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging generator-meteor-stock across your stack and pipelines.
If you installed it — respond
generator-meteor-stock 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 generator-meteor-stock 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 generator-meteor-stock 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. generator-meteor-stock on npm has been identified as a malicious package (version 0.1.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-f53h-6gfq-fcmj

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks generator-meteor-stock-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