Which versions of @silgi/ecosystem are malicious?

The following npm versions of @silgi/ecosystem are flagged malicious: 0.7.6. Treat any of these as compromised.

How do I remediate @silgi/ecosystem if I installed it?

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

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

Yes — @silgi/ecosystem is associated with the GHSA-vc6q-5wm6-qxr9 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/ecosystem 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/ecosystem (version 0.7.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @silgi/ecosystem across your stack and pipelines.

Malicious package

@silgi/ecosystemnpm

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

MAL-2025-191313

Immediate action

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

npm uninstall @silgi/ecosystem

What this malware does

The package @silgi/ecosystem 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.7.6

Indicators of compromise (SHA-256)

598e26a93472b3a603460f980046d3ff87b830ae1970124717caeb9c9aa01f51

e05b24c2b8b197e85ebbafbc2eef89e4b3c94f02b7519a3fe93b514a763e0501

f1476f1384de83c5e5ccae6b60fbcf5794fca7387b8904c42125a65fabab6051

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

Campaign

GHSA-vc6q-5wm6-qxr9

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @silgi/ecosystem-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