adbf@1.0.152
adbf
AI Security Review
scanned 23d ago · by lpm-firewall-aiThe source exposes a user-triggered arbitrary-destination request and header-forwarding mechanism inside an unusually opaque bundle. There is no install-time trigger or confirmed exfiltration sink, so blocking is not supported.
Decision evidence
public snapshot- The manifest exposes index.js through the adbf command and contains no install lifecycle hook.
- The bundled page accepts a user-provided URL, derives its origin, requests an auth path on that origin, and sends the result as a custom header when fetching that URL.
- The entrypoint is heavily obfuscated, preventing a reliable benign-purpose assessment.
- No package lifecycle script automatically runs the entrypoint during installation.
- The observed network flow is activated through the command and page interaction, not automatically on import.
Source & flagged code
12 flagged · loading sourceSource executes local commands and sends command output to an external endpoint.
index.jsView on unpkg · L1Source appears to collect browser login credentials for exfiltration.
index.jsView on unpkg · L1Source fetches a remote non-code asset, decodes its contents, and dynamically executes the decoded payload.
index.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to adbf@1.0.152.
See all versions of adbf for other recorded verdicts.
- Review the evidence and your use of adbf@1.0.152 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.