Which versions of sa-id-gen are malicious?

The following npm versions of sa-id-gen are flagged malicious: 1.0.4, 1.0.5. Treat any of these as compromised.

How do I remediate sa-id-gen if I installed it?

sa-id-gen 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 sa-id-gen — how do I know if it already compromised me?

If sa-id-gen 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 sa-id-gen part of a known attack campaign?

Yes — sa-id-gen is associated with the GHSA-67cw-9phh-xmf8 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 sa-id-gen 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 sa-id-gen (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sa-id-gen across your stack and pipelines.

Malicious package

sa-id-gennpm

Malicious code in sa-id-gen (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191009

Immediate action

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

npm uninstall sa-id-gen

What this malware does

The package sa-id-gen 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.0.41.0.5

Indicators of compromise (SHA-256)

3f0da651d111107f348b8807e1fabc4c0ad1125e1af1e268745224c9d81c77fc

df00f4b56b9be72c09e3f99938b4c41900b44a98e65eb46896c30209f7f0810d

6d026f21ebedc819658ff1afdabcea8157b6697a7f43a746f1605904deb2ff90

7bd85b05fab5fd3ee5256304972605b4d36f18e879102e2d8e90670be2317689

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

Campaign

GHSA-67cw-9phh-xmf8

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks sa-id-gen-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