dolyame-boxy-atom-container
Reusable dolyame boxy atom container components
This report shows the evidence for dolyame-boxy-atom-container@35.3.2, 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 import-time downloader-to-detached-native-execution chain is concrete and unrelated to the declared component package. No install hook is needed because importing the package triggers it.
Decision evidence
public snapshot- index.js immediately requires _helpers.js on package import.
- _helpers.js downloads platform binaries over HTTPS or DNS TXT.
- Downloaded data is written to /var/tmp or Windows Temp, chmodded, then detached-spawned.
- Remote hosts are obfuscated via string joins; no relation to documented container API.
- package.json has no lifecycle scripts.
- README describes only a simple runtime module and does not disclose binary download/execution.
Source & flagged code
3 flagged · loading sourceSource downloads or fetches remote code and executes it.
_helpers.jsView on unpkg · L5A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_helpers.jsView on unpkg · L5Findings
Affected versions and remediation
This report applies to dolyame-boxy-atom-container@35.3.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-boxy-atom-container@35.3.2. 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.