registry / Remote code execution / boxy-devtools-tokens
boxy-devtools-tokens
Boxy devtools tokens provider for microservice architecture
This report shows the evidence for boxy-devtools-tokens@35.9.9, 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 concrete import-time remote binary retrieval and execution, unrelated to the stated token-provider function. No lifecycle hook is needed because the entrypoint triggers the payload chain.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of index.js.
Impact
Arbitrary native code execution under the importing process's user account.
Mechanism
remote payload download, temp-file drop, and detached execution
Attack narrative
A normal require of index.js silently loads _compat.js. That module obtains a platform-specific binary from obfuscated external hosts, or reconstructs a payload through DNS TXT records. When a payload exceeds its threshold, it writes it to a temporary executable file, makes it executable on Unix, and starts it detached through a shell or cmd.exe. The token-manager export does not require this behavior.
AI rationale
This is concrete import-time remote binary retrieval and execution, unrelated to the stated token-provider function. No lifecycle hook is needed because the entrypoint triggers the payload chain.
Evidence
package.jsonindex.js_compat.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints8
oob-worker.c.f99-9b3.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf100-416.workers.devoob-worker.cf101-adf.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:26 imports _compat.js on every package import.
- _compat.js downloads platform binaries from four obfuscated workers.dev hosts.
- _compat.js falls back to DNS TXT payload retrieval from wel1.ru domains.
- _compat.js writes the payload to /var/tmp or Windows Temp, chmods it, then detached-spawns it.
- _compat.js suppresses errors/output and uses a temporary stamp to limit repeats.
Evidence against
- package.json has no lifecycle scripts.
- index.js also contains a functional in-memory TokenManager.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_compat.jsView file
2L3: const https = require("https");
L4: const path = require("path");
...
L45: const STAMP_TTL = 19940;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L90: try {
L91: require("dns").resolveTxt(d, (e, rr) => {
L92: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_compat.jsView on unpkg · L22Trigger-reachable chain: manifest.main -> index.js -> _compat.js
L2:
L3: const https = require("https");
L4: const path = require("path");
...
L45: const STAMP_TTL = 19940;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L90: try {
L91: require("dns").resolveTxt(d, (e, rr) => {
L92: if (e || !rr || !rr.length) return r("");
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_compat.jsView on unpkg · L2117try {
L118: const cp = require("child_process");
L119: if (isWin) {
Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_compat.js
CriticalTrigger Reachable Dangerous Capability_compat.js
HighChild Process_compat.js
HighKnown Malware Source Similarity_compat.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to boxy-devtools-tokens@35.9.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing boxy-devtools-tokens@35.9.9. 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.