Which versions of internallib_v392 are malicious?

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

How do I remediate internallib_v392 if I installed it?

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

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

Yes — internallib_v392 is associated with the GHSA-j9qq-rx28-vcjh, IN-MAL-2026-017621, IN-MAL-2026-017622 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_v392 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_v392 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging internallib_v392 across your stack and pipelines.

Malicious package

internallib_v392npm

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

Malicious code in internallib_v392 (npm)

MAL-2026-13924

Immediate action

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

npm uninstall internallib_v392

What this malware does

index.js exports a function that invokes /bin/bash -c to curl a remote reverse-shell script from reverse-shell.sh and pipe it to sh, targeting the hardcoded IP 10.0.72.234 on port 443. When the exported API is called by a consumer, the installer's host fetches and executes attacker-controlled shell code, granting the attacker at 10.0.72.234:443 a reverse shell on the installer's machine. The package metadata is minimal (empty description/author) and the package name has a typosquat-like shape, consistent with a malicious drop rather than a legitimate library.

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

2 flagged

1.0.32.0.3

Indicators of compromise (SHA-256)

aa4bddc6797daac48407afa943d29965a1909b4e02e32d61956c34f2a1bbbe0f

29fa6db9e4a601df500639714e53f29cde2413c54a6ec31ea6bf38fbb0aabd2f

539e252df6b0011863bbe2cad18bba748b7d7ff2c352e7ab34330cb13de6239b

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_v392 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging internallib_v392 across your stack and pipelines.
If you installed it — respond
internallib_v392 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_v392 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_v392 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_v392 on npm has been identified as a malicious package (versions 1.0.3, 2.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-j9qq-rx28-vcjhIN-MAL-2026-017621IN-MAL-2026-017622

References

Credits

Amazon Inspector · finder

Detect & block this

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