Which versions of github-action-for-generator are malicious?

The following npm versions of github-action-for-generator are flagged malicious: 2.1.27, 2.1.28. Treat any of these as compromised.

How do I remediate github-action-for-generator if I installed it?

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

If github-action-for-generator 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 github-action-for-generator part of a known attack campaign?

Yes — github-action-for-generator is associated with the GHSA-r948-2g4j-wcwx 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 github-action-for-generator 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 github-action-for-generator (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging github-action-for-generator across your stack and pipelines.

Malicious package

github-action-for-generatornpm

Malicious code in github-action-for-generator (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190845

Immediate action

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

npm uninstall github-action-for-generator

What this malware does

The package github-action-for-generator 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

2.1.272.1.28

Indicators of compromise (SHA-256)

f113ada2d15b58b0f4d27cf7554da50cc65dcdfc103616cd54e31b2a77f6d867

456b535e2ac0dbf2257fbb995ee5d72a53c3cfc544a0c9fb477f0c7eb20477d1

597aa3cf8958fae580a08b96dfdf363725ef3409f2a1c962b1706888d454fa03

45d3f617460c732c1416984e1544e5b96c47ff933b78ba386532b22276cc7cbf

7b020c3058b2a7560a89a5cc742fb77bec0a7d5a2067d4f4371463c52ef14913

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

Campaign

GHSA-r948-2g4j-wcwx

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks github-action-for-generator-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