Which versions of native_dep are malicious?

The following npm versions of native_dep are flagged malicious: 2.0.1, 2.0.2, 99.10.0. Treat any of these as compromised.

How do I remediate native_dep if I installed it?

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

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

Yes — native_dep is associated with the GHSA-j72j-g5w7-jj7f 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 native_dep 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 native_dep (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging native_dep across your stack and pipelines.

Malicious package

native_depnpm

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

MAL-2026-1455

Immediate action

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

npm uninstall native_dep

What this malware does

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

The OpenSSF Package Analysis project identified 'native_dep' @ 99.10.0 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

3 flagged

2.0.12.0.299.10.0

Indicators of compromise (SHA-256)

3ed70022a5a0b7ab4917da3358de4f8ea6d2650bce8bfe56b3aef209e102f796

82c72cd2d9b6b62e984b49dcdada595372d60bcef634e69f6c1f254b09044f2b

62fe85371a2100e5ef011320b6359b52313ad88ec2d96d7ad1eed181d13143ec

cf8cbbcc5fef314cdaa3a8b8c2d15e298a0c5f1c444084cc36a8dc36a95b7da1

96b85414b77cb51face1caae1f5ab5ab4ba386fb95ba1c8594ac3ce47a6cb19d

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

Campaign

GHSA-j72j-g5w7-jj7f

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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