Which versions of internallib_v811 are malicious?

The following npm versions of internallib_v811 are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate internallib_v811 if I installed it?

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

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

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

Search your lockfiles and build artifacts for internallib_v811 (version 1.0.1).

Malicious package

internallib_v811npm

Advisory published Nov 13, 2026Updated Nov 13, 2026

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

Malicious code in internallib_v811 (npm)

MAL-2026-19230

Immediate action

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

npm uninstall internallib_v811

What this malware does

package.json declares the dependency internallib-helper with a source of http://10.0.77.5:8000/internallib-helper-1.0.1.tgz — a plain-HTTP tarball URL on a private IP, not a registry version range. On npm install, npm fetches whatever bytes that host serves and installs them, executing any lifecycle scripts inside the fetched tarball, with no version pin and no integrity check. The transport is cleartext HTTP, so any party able to intercept traffic to 10.0.77.5:8000 can substitute the delivered archive. The shipped index.js is a trivial stub, so the manifest line itself is the install-time code-delivery mechanism. The dependency name internallib-helper closely mirrors the package's own name internallib_v811, matching an internal-package / dependency-confusion lure shape.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

cee312ec1c8c2f9177c54179b22a3f493ba30ee35b5f3c41952b5bdbbfd4eed0

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-022774

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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