boxy-maker-wave
Internal boxy maker wave module for platform services
This report shows the evidence for boxy-maker-wave@35.2.1, 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 payload execution chain, not ordinary telemetry. The absence of lifecycle hooks does not mitigate execution triggered by importing the documented package entrypoint.
Decision evidence
public snapshot- index.js imports _platform.js on every package require.
- _platform.js downloads platform binaries from worker hosts or DNS TXT records.
- _platform.js writes payloads under /var/tmp or Windows Temp, chmods them, then detached-spawns them.
- _platform.js embeds worker endpoints and dl.wel1.ru DNS fallback domains.
- package.json has no lifecycle hooks.
- Public BoxyMakerWave API is otherwise minimal.
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.jsFindings
Affected versions and remediation
This report applies to boxy-maker-wave@35.2.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing boxy-maker-wave@35.2.1. 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.