Which versions of create-silgi are malicious?

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

How do I remediate create-silgi if I installed it?

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

If create-silgi was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find create-silgi across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for create-silgi (version 0.3.1).

Malicious package

create-silginpm

Advisory published Nov 25, 2025Updated Dec 1, 2025

create-silgi is a confirmed malicious npm package (MAL-2025-191392) that steals credentials and exfiltrates sensitive data (malicious version 0.3.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in create-silgi (npm)

MAL-2025-191392

Immediate action

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

npm uninstall create-silgi

What this malware does

The package create-silgi was found to contain malicious code.

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.3.1

Indicators of compromise (SHA-256)

28a8282774c9a122fb460bbd03c4e761f56c4e58ae130f85ecdb0025d5af9a6c

8d1bd1ddfab5f3ea6caf4f09a93f2ef08f7298e2d68892949e0a6f2975cd1b78

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for create-silgi (version 0.3.1).
If you installed it — respond
create-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 create-silgi was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. create-silgi on npm has been identified as a malicious package (version 0.3.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

Amazon Inspector · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database