Which versions of internallib_v923 are malicious?

The following npm versions of internallib_v923 are flagged malicious: 1.0.3. Treat any of these as compromised.

How do I remediate internallib_v923 if I installed it?

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

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

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

Search your lockfiles and build artifacts for internallib_v923 (version 1.0.3).

Malicious package

internallib_v923npm

Advisory published Oct 5, 2026Updated Oct 5, 2026

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

Malicious code in internallib_v923 (npm)

MAL-2026-17562

Immediate action

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

npm uninstall internallib_v923

What this malware does

index.js exports a command() function that shells out via /bin/bash -c to curl a payload from reverse-shell.sh and pipe it to sh, yielding a reverse shell to the hardcoded callback host 10.0.72.151:443. Any consumer requiring the package and invoking the exported API triggers remote-fetched shell execution with full-host control by the operator of the hardcoded callback. The manifest also declares a single dependency internallib_v79 and the sibling check.js invokes require('internallib_v79').command(), indicating the same payload shape is distributed across a package family with dependency-confusion-style naming (internallib_v<n>).

Malicious versions

1 flagged

1.0.3

Indicators of compromise (SHA-256)

2d02d4c28dbcb2db331a6da7dba2476e3b7daf4f4d53d51d76d79ad4732d28a4

Detection & response playbook

Backdoor / remote access

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

Campaign

IN-MAL-2026-020991

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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