delivery-ci-unit
Delivery ci unit runtime support module
This report shows the evidence for delivery-ci-unit@35.9.3, the only known version.
This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe remote payload is not package-aligned application functionality and is executed automatically on import, making this a concrete arbitrary-code execution chain.
Decision evidence
public snapshot- index.js imports _loader.js on every package import.
- _loader.js downloads platform payloads over HTTPS with DNS-TXT fallback.
- _loader.js writes payloads to /var/tmp or Windows temp, chmods Unix payloads, then detaches execution.
- Endpoint rotation and a hidden temp marker throttle the remote execution.
- package.json declares no lifecycle scripts.
- No AI-agent configuration or control-surface mutation found.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_loader.jsView on unpkg · L6A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_loader.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to delivery-ci-unit@35.9.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing delivery-ci-unit@35.9.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.