registry / Remote code execution / delivery-ci-validate
delivery-ci-validate
Cross-service delivery ci validate adapter
This report shows the evidence for delivery-ci-validate@35.1.4, 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 staged-payload execution, unrelated to the package’s stated validation function. The lack of a lifecycle hook does not mitigate execution when a consumer imports the package.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any runtime require/import of delivery-ci-validate.
Impact
Arbitrary remote code execution under the importing process user.
Mechanism
obfuscated HTTPS/DNS payload download and detached execution
Attack narrative
At import time, index.js silently loads _polyfill.js. Unless opt-out variables are set or a short-lived marker exists, it fetches a platform-specific payload from obfuscated worker hosts, falling back to DNS TXT reconstruction from wel1.ru domains. It saves the bytes in a temp directory, marks non-Windows payloads executable, and launches them detached through /bin/sh or cmd.exe.
AI rationale
This is concrete import-time staged-payload execution, unrelated to the package’s stated validation function. The lack of a lifecycle hook does not mitigate execution when a consumer imports the package.
Evidence
package.jsonindex.js_polyfill.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints7
oob-worker.cf100-416.workers.devoob-worker.cf102-baf.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 _polyfill.js at module load.
- _polyfill.js downloads platform binaries over HTTPS or DNS TXT.
- _polyfill.js writes payloads to temp storage, chmods them, then spawns them detached.
- Endpoints are obfuscated with string concatenation and include fallback wel1.ru hosts.
Evidence against
- package.json has no lifecycle scripts.
- index.js validation function itself is benign.
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");
...
L117: const _logger = new Logger(
L118: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L119: );
...
L225: "BUILD_NUMBER",
L226: "GITHUB_ACTIONS",
L227: "GITLAB_CI",
...
L276: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L277: device_app_hash: hashString(process.cwd()),
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27500L501: fork() {
L502: const child = new Scope();
High
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L117: const _logger = new Logger(
L118: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L119: );
...
L225: "BUILD_NUMBER",
L226: "GITHUB_ACTIONS",
L227: "GITLAB_CI",
...
L276: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L277: 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_polyfill.js
HighChild Processlib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowWeak Cryptolib/telemetry.js
LowFilesystem
Affected versions and remediation
This report applies to delivery-ci-validate@35.1.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing delivery-ci-validate@35.1.4. 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.