Which versions of ids-enterprise-ng are malicious?

The following npm versions of ids-enterprise-ng are flagged malicious: 20.1.6. Treat any of these as compromised.

How do I remediate ids-enterprise-ng if I installed it?

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

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

Yes — ids-enterprise-ng is associated with the GHSA-qcj4-hjhm-cmvp 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 ids-enterprise-ng 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 ids-enterprise-ng (version 20.1.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ids-enterprise-ng across your stack and pipelines.

Malicious package

ids-enterprise-ngnpm

Malicious code in ids-enterprise-ng (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191108

Immediate action

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

npm uninstall ids-enterprise-ng

What this malware does

The package ids-enterprise-ng 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

20.1.6

Indicators of compromise (SHA-256)

9afc4d16b7a79bf73f739952704a2f8c360ea01812d4882f69e191bc3cf1e455

2a75fd10c5b7b6c1cabe7b06870617377927117422442f5e523df83e268c7281

02ae15f729fa23d65989e0f3873d023de175ecf54bb2b230df46861c246bf7df

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

Campaign

GHSA-qcj4-hjhm-cmvp

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ids-enterprise-ng-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