Which versions of @silgi/openapi are malicious?

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

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

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

If @silgi/openapi 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.

Is @silgi/openapi part of a known attack campaign?

Yes — @silgi/openapi is associated with the GHSA-jjgq-j9mv-qvww 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/openapi across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @silgi/openapi (version 0.7.4).

Part of a larger attack: @silgi published 10 malicious packages. See the full campaign →

Malicious package

@silgi/openapinpm

Advisory published Nov 24, 2025Updated Dec 1, 2025

@silgi/openapi is a confirmed malicious npm package (MAL-2025-191316) that steals credentials and exfiltrates sensitive data (malicious version 0.7.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @silgi/openapi (npm)

MAL-2025-191316

Immediate action

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

npm uninstall @silgi/openapi

What this malware does

The package @silgi/openapi 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.4

Indicators of compromise (SHA-256)

8b55c53f201446b55adf4114bcfbf42f56246598c62e998a916283ece2e19cc9

3c5eda9815ba5af459be6844eab3b3e9f5cb4615e738904bd8214eb62a2c93e7

da37d75ae054be71f7d9d4913bf4e5b1c0e7249774278432c33d89d871d99f28

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @silgi/openapi (version 0.7.4).
If you installed it — respond
@silgi/openapi 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/openapi 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. @silgi/openapi on npm has been identified as a malicious package (version 0.7.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jjgq-j9mv-qvww

References

Credits

Amazon Inspector · finder

Detect & block this

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