Which versions of ids-enterprise-typings are malicious?

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

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

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

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

Yes — ids-enterprise-typings is associated with the GHSA-jvr2-6364-4x9q 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-typings 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-typings (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-typings across your stack and pipelines.

Malicious package

ids-enterprise-typingsnpm

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

MAL-2025-191109

Immediate action

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

npm uninstall ids-enterprise-typings

What this malware does

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

84e51fb84014e2b373221d77df649c0a62dd1fd4ee836f91cd35a6af83167e46

d4fc430d4b6588549e8cd4b9ca432e95f5afca875b1a7571cb521e04a045b6c9

d8d2289786c3e4396ada63a5a2651f54fc6a55d011e2b5f8acccb8aa21b11cab

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-typings (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-typings across your stack and pipelines.
If you installed it — respond
ids-enterprise-typings 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-typings 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-typings 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-typings 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-jvr2-6364-4x9q

References

Credits

Amazon Inspector · finder

Detect & block this

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