registry / Remote code execution / boxy-tokens
boxy-tokens
Internal boxy tokens module for platform services
This report shows the evidence for boxy-tokens@35.5.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-aiSource inspection confirms an import-time remote payload download-and-execute chain; it is not a benign telemetry primitive.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of boxy-tokens.
Impact
Unconsented arbitrary native code execution under the importing process user.
Mechanism
Remote binary download, DNS fallback, temp-file drop, and detached execution.
Attack narrative
The package’s normal import path requires setup.js. That module fetches a platform-specific opaque binary from concealed workers.dev endpoints, with DNS TXT/base64 fallback domains, drops it under /var/tmp or Windows Temp, marks it executable on Unix, and starts it detached through /bin/sh or cmd.exe. This is a concrete remote-code-execution payload chain unrelated to the advertised token API.
AI rationale
Source inspection confirms an import-time remote payload download-and-execute chain; it is not a benign telemetry primitive.
Evidence
package.jsonindex.jssetup.jslib/telemetry.js
Network endpoints7
oob-worker.cf101-adf.workers.devoob-worker.cf100-416.workers.devoob-worker.cf103-070.workers.devsdk.dl.wel1.ruext.dl.wel1.rupkg.dl.wel1.runet.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 ./setup on every package import.
- setup.js downloads opaque platform binaries from obfuscated workers.dev hosts or DNS TXT records.
- setup.js writes payloads to a temp directory, chmods them executable, then launches them detached via shell/cmd.
- lib/telemetry.js duplicates the download-to-temp-and-execute mechanism.
Evidence against
- package.json has no lifecycle scripts.
- TokenManager itself is an in-memory token store.
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");
...
L116: const _logger = new Logger(
L117: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L118: );
...
L224: "BUILD_NUMBER",
L225: "GITHUB_ACTIONS",
L226: "GITLAB_CI",
...
L275: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L276: device_app_hash: hashString(process.cwd()),
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27494L495: fork() {
L496: const child = new Scope();
High
•matchType = normalized_sha256
matchedPackage = boxy-add-link@35.7.5
matchedPath = lib/telemetry.js
matchedIdentity = npm:Ym94eS1hZGQtbGluaw:35.7.5
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 Capabilitysetup.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-tokens@35.5.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing boxy-tokens@35.5.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.