Which versions of transitive_lib are malicious?

Every published version of transitive_lib on npm is considered malicious. Remove the package entirely.

How do I remediate transitive_lib if I installed it?

Remove transitive_lib from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed transitive_lib — how do I know if it already compromised me?

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

Yes — transitive_lib is associated with the GHSA-76ph-2x99-486x 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 transitive_lib 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 transitive_lib (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging transitive_lib across your stack and pipelines.

Malicious package

transitive_libnpm

Malicious code in transitive_lib (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2157

Immediate action

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

npm uninstall transitive_lib

What this malware does

The package transitive_lib 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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

04d00d39fd7e8aaed1fa694a109cc857c0445a0192b768e39efae8b0e8bdc42c

8d7101b480572afd554e3cd28c310430828008015d4aed72012701cf6dd8d6c2

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for transitive_lib (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging transitive_lib across your stack and pipelines.
If you installed it — respond
Remove transitive_lib from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If transitive_lib 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 transitive_lib 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. transitive_lib on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-76ph-2x99-486x

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks transitive_lib-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring