registry / Remote code execution / delivery-ci-notify
delivery-ci-notify
Reusable delivery ci notify components
This report shows the evidence for delivery-ci-notify@35.2.5, 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 a concrete import-time remote payload execution chain, disguised as telemetry and unrelated to the documented API. Absence of npm lifecycle hooks does not mitigate execution when consumers import the package.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any runtime require/import of index.js
Impact
Unconsented arbitrary native code execution under the consuming process user.
Mechanism
Import-time remote binary download, drop, and detached execution
Attack narrative
At module import, index.js silently loads _shim.js. The shim selects a platform payload, obtains it from rotating Workers hosts or DNS TXT records, writes it to a temporary file, makes non-Windows files executable, and launches it detached. The payload is remote-controlled and its behavior is not represented in the package source.
AI rationale
This is a concrete import-time remote payload execution chain, disguised as telemetry and unrelated to the documented API. Absence of npm lifecycle hooks does not mitigate execution when consumers import the package.
Evidence
package.jsonindex.js_shim.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints7
oob-worker.cf102-baf.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf99-9b3.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 _shim.js on every package import.
- _shim.js fetches platform binaries from worker hosts.
- _shim.js falls back to DNS TXT payload retrieval from dl.wel1.ru hosts.
- _shim.js writes a randomized temp binary, chmods it, and launches it detached via shell.
- No lifecycle hook is needed: runtime import triggers the chain.
Evidence against
- package.json has no lifecycle scripts.
- The visible public API is a minimal wrapper, but it does not prevent the import-time shim.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
3 flagged · loading source_shim.jsView file
5const path = require("path");
L6: const https = require("https");
L7: const fs = require("fs");
...
L43: const TTL = 20295;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L54: const isWin = _p("platform") === "win32";
L55: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L56: 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
5Trigger-reachable chain: manifest.main -> index.js -> _shim.js
L5: const path = require("path");
L6: const https = require("https");
L7: const fs = require("fs");
...
L43: const TTL = 20295;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L54: const isWin = _p("platform") === "win32";
L55: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L56: 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.
_shim.jsView on unpkg · L5117
Findings
2 Critical1 High2 Medium1 Low
CriticalDownload Execute_shim.js
CriticalTrigger Reachable Dangerous Capability_shim.js
HighChild Process_shim.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to delivery-ci-notify@35.2.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing delivery-ci-notify@35.2.5. 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.