registry / Remote code execution / boxy-maker
boxy-maker
Cross-service boxy maker adapter
This report shows the evidence for boxy-maker@35.4.8, 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 remote payload execution chain is concrete and independent of lifecycle scripts. The large telemetry module contains the same downloader/launcher pattern but is not needed to establish the attack.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of the main index.js entrypoint.
Impact
Arbitrary attacker-controlled native code runs as the importing process user.
Mechanism
import-time staged binary download, drop, chmod, and detached execution
Attack narrative
The public entrypoint silently loads _bridge.js. Its module-load init function fetches a platform payload from obfuscated workers.dev hosts, falling back to chunked DNS TXT records under wel1.ru. It saves the bytes in a temporary file, marks Unix payloads executable, and starts them detached through /bin/sh or cmd.exe. This is an unconsented remote code-execution chain activated merely by importing the package.
AI rationale
The import-time remote payload execution chain is concrete and independent of lifecycle scripts. The large telemetry module contains the same downloader/launcher pattern but is not needed to establish the attack.
Evidence
package.jsonindex.js_bridge.jslib/telemetry.jsREADME.md/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints7
oob-worker.cf102-baf.workers.dev/pkg/packageoob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packagesdk.dl.wel1.ru
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports _bridge on every package import.
- _bridge.js immediately invokes init() at module load.
- _bridge.js downloads platform binaries from obfuscated workers.dev hosts or DNS TXT.
- Downloaded bytes are written to temp storage, chmodded, and detached-spawned via shell/cmd.
- DNS fallback hosts are obfuscated wel1.ru domains.
Evidence against
- package.json contains no lifecycle scripts.
- README.md exposes only a benign-looking require example.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
5 flagged · loading sourcelib/telemetry.jsView file
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L121: const _logger = new Logger(
L122: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L123: );
...
L229: "BUILD_NUMBER",
L230: "GITHUB_ACTIONS",
L231: "GITLAB_CI",
...
L280: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L281: device_app_hash: hashString(process.cwd()),
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27495L496: fork() {
L497: const child = new Scope();
High
•matchType = normalized_sha256
matchedPackage = statist-browser-typed-client-coretech.web.metrics@20.1.8
matchedPath = lib/telemetry.js
matchedIdentity = npm:[redacted]:20.1.8
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
lib/telemetry.jsView on unpkgFindings
2 Critical2 High2 Medium2 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capability_bridge.js
HighChild Processlib/telemetry.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowWeak Cryptolib/telemetry.js
LowFilesystem
Affected versions and remediation
This report applies to boxy-maker@35.4.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing boxy-maker@35.4.8. 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.