boxy-demo-tokens
Internal boxy demo tokens module for platform services
This report shows the evidence for boxy-demo-tokens@35.2.7, 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-aiDirect source inspection confirms a reachable import-time downloader and executor, not merely telemetry behavior. The lack of install hooks does not mitigate runtime execution on package import.
Decision evidence
public snapshot- index.js imports ./_bridge during every module load.
- _bridge.js downloads platform payloads from obfuscated workers.dev hosts.
- _bridge.js falls back to DNS TXT payload retrieval from wel1.ru domains.
- _bridge.js writes the downloaded payload to /var/tmp or Windows Temp, marks it executable, and spawns it.
- No integrity check or signature verification is performed before execution.
- package.json has no lifecycle scripts.
- index.js token manager itself is an in-memory token utility.
Source & flagged code
6 flagged · loading sourceSource downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27Source file is highly similar to a previously finalized malicious package; route for source-aware review.
lib/telemetry.jsFindings
Affected versions and remediation
This report applies to boxy-demo-tokens@35.2.7.
The versions list below shows the verdict for each recorded version.
- Avoid installing boxy-demo-tokens@35.2.7. 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.