requester-lbnpm
Advisory published Updated
requester-lb is a confirmed malicious npm package (MAL-2026-20217) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.9, 1.0.14, 1.0.15). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in requester-lb (npm)
What this malware does
The package advertises itself as an HTTP/DNS requester CLI but ships a test.sh whose primary purpose is credential theft. test.sh splits sensitive commands into ~10 single-letter shell variables that are concatenated and passed to eval, reconstructing printenv and a command that reads the in-pod Kubernetes service-account token from /var/run/secrets/kubernetes.io/serviceaccount/token into $DEBUG_FILE, then invokes ./oc login --token=$DEBUG_FILE --server=$SERV --insecure-skip-tls-verify to authenticate the current cluster identity to a server specified via the SERV environment variable. The string-fragment obfuscation has no benign purpose and is a deliberate scanner-evasion pattern. The package layout corroborates the disguise: package.json declares main: index.js but no index.js is shipped, the only legitimate JS (requester.js) is unrelated to the shell payload, and test.sh is not referenced by any npm script — it is a standalone delivery vehicle for an operator or CI job that executes it inside a Kubernetes/OpenShift pod. The payload does not auto-execute on npm install (no lifecycle hook invokes test.sh), but the harm on explicit execution is cluster credential theft and attacker-controlled cluster federation with TLS verification disabled.
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
Search your lockfiles and build artifacts for requester-lb (3 malicious versions).
If you installed it — respond
requester-lb 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 requester-lb 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 requester-lb-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.