boxy-lcd
Internal boxy lcd module for platform services
This report shows the evidence for boxy-lcd@35.2.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-aiThis is a concrete import-time remote code execution chain disguised as telemetry and unrelated to the published adapter API. No lifecycle hook is needed because ordinary package consumption activates it.
Decision evidence
public snapshot- index.js imports ./setup on every package import.
- setup.js downloads platform binaries from oob-worker.cf102-baf.workers.dev and fallback hosts.
- setup.js reconstructs payloads from DNS TXT under *.dl.wel1.ru.
- setup.js writes payloads to temp, chmods them, then launches via shell/child_process.
- package.json has no lifecycle scripts.
- The declared BoxyLcd API is otherwise minimal; malicious setup is hidden from it.
Source & flagged code
5 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.jsView on unpkgFindings
Affected versions and remediation
This report applies to boxy-lcd@35.2.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing boxy-lcd@35.2.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.