Which versions of internallib_v23 are malicious?

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

How do I remediate internallib_v23 if I installed it?

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

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

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

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

Malicious package

internallib_v23npm

Advisory published Oct 6, 2026Updated Oct 6, 2026

internallib_v23 is a confirmed malicious npm package (MAL-2026-17632) 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_v23 (npm)

MAL-2026-17632

Immediate action

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

npm uninstall internallib_v23

What this malware does

index.js line 5 exports a function that invokes /bin/bash to curl https://reverse-shell.sh/10.0.19.80:4443 and pipe the response to a shell, delivering an interactive reverse shell to the hardcoded endpoint 10.0.19.80:4443 on the host where the exported function is called. The destination is a hardcoded private-range IP, there is no authentication, no documentation of the behavior, and the fetched content is executed directly. The package's only exported functionality is this backdoor dropper.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

bf294381eb4f87a0dcccbd00977ac38ab25a8108639c8cc08543c7d0e09b5f36

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for internallib_v23 (version 1.0.1).
If you installed it — respond
internallib_v23 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_v23 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_v23 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-021094

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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