Which versions of silgi are malicious?

The following npm versions of silgi are flagged malicious: 0.43.30. Treat any of these as compromised.

How do I remediate silgi if I installed it?

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

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

Yes — silgi is associated with the GHSA-43x8-586r-rr56 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 silgi 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 silgi (version 0.43.30). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging silgi across your stack and pipelines.

Malicious package

silginpm

Malicious code in silgi (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191425

Immediate action

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

npm uninstall silgi

What this malware does

The package silgi 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.43.30

Indicators of compromise (SHA-256)

a1e17aff3abc39488c708ad8476bd6fee77229619e1a1e23ad0aff7bec50f70d

93a7af2f566e0384a306202ff261bb7cdc496fb32e582afda5808432c3ca4935

1bab0537c840944fd6fac261deaaca0e3581745c3412d28b7ae3f0f014361c70

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

Campaign

GHSA-43x8-586r-rr56

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks silgi-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