registry / Remote code execution / twork-mf-sandbox
twork-mf-sandbox
database access layer
This report shows the evidence for twork-mf-sandbox@20.9.7. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
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 payload execution, concealed behind an unrelated package description and telemetry-style naming. No lifecycle hook is needed because ordinary package import activates it.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Requiring/importing twork-mf-sandbox
Impact
Unconsented arbitrary native code execution in the consuming host.
Mechanism
Remote binary download/DNS payload retrieval followed by temp-file execution
Attack narrative
When a consumer imports index.js, its swallowed-error require loads _bridge.js and calls init(). Unless opt-out environment variables are set, it contacts hard-coded HTTPS hosts and then DNS TXT domains for a payload, stores a binary in a temporary directory, applies executable permissions on Unix, and launches it detached through a shell or cmd.exe.
AI rationale
This is concrete import-time remote payload execution, concealed behind an unrelated package description and telemetry-style naming. No lifecycle hook is needed because ordinary package import activates it.
Evidence
package.jsonindex.js_bridge.jsREADME.mdlib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf101-adf.workers.devoob-worker.cf99-9b3.workers.devoob-worker.cf100-416.workers.devoob-worker.cf103-070.workers.dev
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.js on package import.
- _bridge.js fetches platform payloads from hard-coded worker hosts or DNS TXT records.
- _bridge.js writes payloads to /var/tmp or Windows temp, makes Unix payloads executable, then detached-spawns them.
- The README describes only a database layer; this hidden downloader is unrelated.
Evidence against
- package.json has no lifecycle scripts.
- lib/telemetry.js requires explicit run(opts), but _bridge.js executes independently at import.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
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: );
...
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 · L27496L497: fork() {
L498: 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: );
...
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()),
Low
Weak Crypto
Package source references weak cryptographic algorithms.
Findings
2 Critical1 High2 Medium2 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capability_bridge.js
HighChild Processlib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowWeak Cryptolib/telemetry.js
LowFilesystem
Affected versions and remediation
This report applies to twork-mf-sandbox@20.9.7.
The versions list below shows the verdict for each recorded version.
- Avoid installing twork-mf-sandbox@20.9.7. 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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.