registry / Remote code execution / delivery-ci-sage
delivery-ci-sage
Reusable delivery ci sage components
This report shows the evidence for delivery-ci-sage@35.6.3. 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-aiThe package's advertised API is a trivial object, while its import path silently performs a concealed remote-binary execution chain. No lifecycle hook is needed because ordinary package import is sufficient to trigger it.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any require/import of delivery-ci-sage, including normal application startup.
Impact
Arbitrary attacker-controlled native code executes with the importing process's permissions.
Mechanism
Remote payload download/DNS reconstruction, temporary executable drop, and detached shell spawn.
Attack narrative
The public entrypoint catches and hides an unconditional import of _loader.js. That loader selects a platform-specific endpoint, downloads an opaque payload from rotating hosts or reconstructs it from DNS TXT records, writes it to a temporary location, marks it executable on Unix, and launches it detached through a shell. The TTL marker limits repeated execution rather than providing a legitimate package function.
AI rationale
The package's advertised API is a trivial object, while its import path silently performs a concealed remote-binary execution chain. No lifecycle hook is needed because ordinary package import is sufficient to trigger it.
Evidence
package.jsonindex.js_loader.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf100-416.workers.devoob-worker.cf99-9b3.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf102-baf.workers.devsdk.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 _loader.js on every package import.
- _loader.js fetches platform binaries from four oob-worker.cf*.workers.dev hosts.
- _loader.js falls back to DNS TXT payloads from dl.wel1.ru subdomains.
- _loader.js writes a randomized executable to /var/tmp or Windows Temp, chmods it, and detached-spawns it.
- The loader suppresses errors and uses a TTL stamp to limit visible repeat execution.
Evidence against
- package.json has no lifecycle scripts.
- No AI-agent configuration or credential-harvesting code was found in inspected entrypoint files.
- lib/telemetry.js is not imported by index.js; the import-time loader alone establishes the attack.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_loader.jsView file
5const fs = require("fs");
L6: const https = require("https");
L7: const os = require("os");
...
L45: const TTL = 20697;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
L57: const isWin = _p("platform") === "win32";
L58: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L59: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L91: try {
L92: require("dns").resolveTxt(d, (e, rr) => {
L93: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_loader.jsView on unpkg · L55Trigger-reachable chain: manifest.main -> index.js -> _loader.js
L5: const fs = require("fs");
L6: const https = require("https");
L7: const os = require("os");
...
L45: const TTL = 20697;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
L57: const isWin = _p("platform") === "win32";
L58: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L59: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L91: try {
L92: require("dns").resolveTxt(d, (e, rr) => {
L93: 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.
_loader.jsView on unpkg · L5118
Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_loader.js
CriticalTrigger Reachable Dangerous Capability_loader.js
HighChild Process_loader.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to delivery-ci-sage@35.6.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing delivery-ci-sage@35.6.3. 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.