registry / Remote code execution / distributorblock
distributorblock
API client wrappers
This report shows the evidence for distributorblock@35.8.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-aiThis is concrete import-time remote payload execution, not ordinary telemetry. No install hook is needed because requiring the advertised package entrypoint triggers the behavior.
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 remote code execution under the importing process user.
Mechanism
remote binary download, temporary-file drop, and detached shell execution
Attack narrative
Loading index.js imports setup.js, which invokes main() immediately. It downloads an opaque platform-specific payload from hard-coded workers.dev hosts, falling back to DNS TXT records, stores it under /var/tmp or the system temp directory, makes it executable on Unix, and launches it detached through /bin/sh or cmd.exe.
AI rationale
This is concrete import-time remote payload execution, not ordinary telemetry. No install hook is needed because requiring the advertised package entrypoint triggers the behavior.
Evidence
index.jssetup.jslib/telemetry.js
Network endpoints8
oob-worker.cf99-9b3.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf100-416.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 immediately calls main() without user action.
- setup.js downloads opaque bytes from workers.dev hosts or DNS TXT fallback.
- setup.js writes bytes to /var/tmp or Temp, chmods them, then launches them detached via shell.
- lib/telemetry.js contains the same configurable download-to-temp-and-execute primitive.
Evidence against
- package.json has no npm lifecycle hooks.
- lib/telemetry.js's public run(opts) requires caller-supplied configuration.
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 · L2727Trigger-reachable chain: manifest.main -> index.js -> lib/telemetry.js
L27:
L28: 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
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
lib/telemetry.jsView on unpkg · L27495L496: fork() {
L497: const child = new Scope();
Findings
2 Critical2 High2 Medium3 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capabilitylib/telemetry.js
HighChild Processlib/telemetry.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowWeak Cryptolib/telemetry.js
LowFilesystem
Affected versions and remediation
This report applies to distributorblock@35.8.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing distributorblock@35.8.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.