Which versions of internallib_v756 are malicious?

The following npm versions of internallib_v756 are flagged malicious: 1.0.7. Treat any of these as compromised.

How do I remediate internallib_v756 if I installed it?

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

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

Yes — internallib_v756 is associated with the IN-MAL-2026-017623, GHSA-933g-5588-v5hp 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_v756 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_v756 (version 1.0.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging internallib_v756 across your stack and pipelines.

Malicious package

internallib_v756npm

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

Malicious code in internallib_v756 (npm)

MAL-2026-13928

Immediate action

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

npm uninstall internallib_v756

What this malware does

index.js (the package main entry) synchronously invokes execSync to spawn /bin/bash -i with stdio redirected through /dev/tcp/10.0.74.63/4444, opening an interactive reverse shell to a hardcoded remote address whenever the module is loaded. The shell spawn is top-level code, so it fires immediately on require()/import of the package with no gating, granting the operator of 10.0.74.63 interactive command execution on the installer's host.

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

1 flagged

1.0.7

Indicators of compromise (SHA-256)

fb9f2ca94c3bf4bd18f73321d08c08130180a3bb66237a4f05f326d0adcf6e06

81650136083716aa3226230e1022003111335d0a20933611188e5f26bbfb72b8

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

Campaign

IN-MAL-2026-017623GHSA-933g-5588-v5hp

References

Credits

Amazon Inspector · finder

Detect & block this

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