registry / Remote code execution / boxy-mif-tokens
boxy-mif-tokens
Boxy mif tokens SDK for internal consumers
This report shows the evidence for boxy-mif-tokens@35.7.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-aiThe hidden import-time loader provides a complete unconsented remote-code-execution chain. Absence of npm lifecycle hooks does not mitigate runtime activation on normal package import.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Runtime import of index.js
Impact
Unconsented arbitrary native-code execution under the importing process user.
Mechanism
Remote binary download/DNS payload retrieval followed by detached execution
Attack narrative
On import, index.js silently requires _bridge.js. That module downloads a platform-targeted binary from obfuscated remote hosts or reconstructs one through DNS TXT records, writes it to a temporary path, marks it executable on Unix, and launches it detached through /bin/sh or cmd.exe. This is a concrete remote payload execution chain unrelated to the documented token API.
AI rationale
The hidden import-time loader provides a complete unconsented remote-code-execution chain. Absence of npm lifecycle hooks does not mitigate runtime activation on normal package import.
Evidence
index.js_bridge.jspackage.json/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf103-070.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf100-416.workers.devoob-worker.cf102-baf.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 _bridge on every package import.
- _bridge.js downloads binary payloads from obfuscated Workers hosts.
- _bridge.js falls back to DNS TXT payload retrieval from wel1.ru hosts.
- _bridge.js writes, chmods, and detached-spawns the downloaded payload.
- The loader suppresses errors and disguises its marker as analytics state.
Evidence against
- package.json has no lifecycle scripts.
- index.js otherwise implements an in-memory token manager.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
4 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: );
...
L230: "BUILD_NUMBER",
L231: "GITHUB_ACTIONS",
L232: "GITLAB_CI",
...
L281: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L282: device_app_hash: hashString(process.cwd()),
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27503L504: fork() {
L505: const child = new Scope();
High
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: );
...
L230: "BUILD_NUMBER",
L231: "GITHUB_ACTIONS",
L232: "GITLAB_CI",
...
L281: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L282: device_app_hash: hashString(process.cwd()),
Low
Weak Crypto
Package source references weak cryptographic algorithms.
Findings
2 Critical1 High3 Medium3 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capability_bridge.js
HighChild Processlib/telemetry.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowWeak Cryptolib/telemetry.js
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to boxy-mif-tokens@35.7.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing boxy-mif-tokens@35.7.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.