internallib_v647npm
Advisory published Updated
internallib_v647 is a confirmed malicious npm package (MAL-2026-19229) that executes malicious code on install (malicious version 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in internallib_v647 (npm)
What this malware does
package.json declares the dependency internallib-helper as a plain-HTTP tarball URL at a bare internal IP: http://10.0.77.5:8000/internallib-helper-1.0.0.tgz. On npm install, npm fetches and installs whatever bytes that endpoint returns and runs any lifecycle scripts contained in the resolved tarball. The source is not the npm registry, there is no version pin, no integrity hash, and no TLS, so the fetched content is unauthenticated and mutable, and any party controlling or able to MITM 10.0.77.5:8000 controls code executed on the installing host. The shipped package source is a minimal stub, so the manifest line itself is the install-time execution vector.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for internallib_v647 (version 1.0.3).
If you installed it — respond
Remove internallib_v647 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_v647 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks internallib_v647-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.