multi-reqs
This report shows the evidence for multi-reqs@1.0.3. 4 of 4 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiDirect source inspection confirms deliberate credential exfiltration on the exported runtime path. The lack of lifecycle scripts limits automatic execution but does not remove the concrete malicious capability.
Decision evidence
public snapshot- index.js exports reqs(token, password) that posts both inputs.
- index.js hard-codes a Discord webhook endpoint.
- Payload labels token and password as account information.
- package.json has no lifecycle scripts.
- Importing index.js alone does not invoke reqs.
Source & flagged code
2 flagged · loading sourceSource appears to send environment or credential material to an external endpoint.
index.jsView on unpkg · L2A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
index.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to multi-reqs@1.0.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing multi-reqs@1.0.3. 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.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.