delivery-ci-pipeline-rulesnpm
delivery-ci-pipeline-rules is a confirmed malicious npm package (MAL-2026-12678) that executes malicious code on install (malicious version 35.9.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in delivery-ci-pipeline-rules (npm)
What this malware does
index.js unconditionally require()s init.js on load. init.js assembles attacker-controlled hostnames from split string fragments joined at runtime (e.g. oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev) and fetches a platform-specific executable via https.get, selecting per-platform payload paths (/pkg/package, /pkg/package.exe, /pkg/loader_mac). The fetched bytes are written to /tmp or %TEMP% under a disguised name (.cache<rnd> or dotnet_diag<rnd>.exe), chmod 0755, then spawned detached via /bin/sh -c or cmd.exe /c. When HTTPS fails, _init.js falls back to a DNS-TXT covert channel over sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, resolving c.<domain> for a chunk count, iterating 0.<domain>..N.<domain>, and base64-decoding the concatenated TXT records into the executable. Host and domain constants are string-fragmented to defeat literal scanners; execution is gated by a ~22000-second cache TTL. Installing or importing this package results in an attacker-controlled binary being fetched from non-publisher infrastructure and executed on the installer's host.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for delivery-ci-pipeline-rules (version 35.9.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging delivery-ci-pipeline-rules across your stack and pipelines.
If you installed it — respond
Remove delivery-ci-pipeline-rules from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If delivery-ci-pipeline-rules was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks delivery-ci-pipeline-rules before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks delivery-ci-pipeline-rules-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.