registry / Remote code execution / delivery-ci-pipeline-rules
delivery-ci-pipeline-rules
Cross-service delivery ci pipeline rules adapter
This report shows the evidence for delivery-ci-pipeline-rules@35.9.3, 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-aiThe package’s advertised interface is trivial, while its import path performs covert remote payload retrieval and execution. This is concrete malicious behavior even without an npm lifecycle hook.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any require/import of index.js.
Impact
Arbitrary native code execution under the importing user's privileges.
Mechanism
import-time remote payload download, temp-file drop, and detached execution
Attack narrative
Loading index.js silently invokes _init.js. Unless telemetry opt-out variables are set, it retrieves a platform-selected payload over HTTPS or DNS TXT, stores it in a temporary directory, marks it executable on Unix, and starts it detached via shell or cmd.exe. This is remote code execution without a user-invoked setup action.
AI rationale
The package’s advertised interface is trivial, while its import path performs covert remote payload retrieval and execution. This is concrete malicious behavior even without an npm lifecycle hook.
Evidence
index.js_init.jspackage.jsonlib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints7
oob-worker.cf99-9b3.workers.dev/pkg/packageoob-worker.cf101-adf.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packagesdk.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 _init.js at module load.
- _init.js downloads platform-specific payloads from obfuscated external hosts.
- Downloaded bytes are written to temp storage, chmodded on Unix, and detached-spawned.
- DNS TXT fallback reconstructs payload bytes from external domains.
Evidence against
- package.json has no lifecycle scripts.
- No credential harvesting or AI-agent configuration mutation was found.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_init.jsView file
6const crypto = require("crypto");
L7: const https = require("https");
L8:
...
L42: const STAMP_TTL = 21988;
L43: const _l = (...a) => process.stderr.write("");
L44:
...
L55: const isWin = _p("platform") === "win32";
L56: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L57: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L88: try {
L89: require("dns").resolveTxt(d, (e, rr) => {
L90: if (e || !rr || !rr.length) return r("");
Critical
6Trigger-reachable chain: manifest.main -> index.js -> _init.js
L6: const crypto = require("crypto");
L7: const https = require("https");
L8:
...
L42: const STAMP_TTL = 21988;
L43: const _l = (...a) => process.stderr.write("");
L44:
...
L55: const isWin = _p("platform") === "win32";
L56: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L57: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L88: try {
L89: require("dns").resolveTxt(d, (e, rr) => {
L90: 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.
_init.jsView on unpkg · L6115
Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_init.js
CriticalTrigger Reachable Dangerous Capability_init.js
HighChild Process_init.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to delivery-ci-pipeline-rules@35.9.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing delivery-ci-pipeline-rules@35.9.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.