delivery-ci-jiranpm
delivery-ci-jira is a confirmed malicious npm package (MAL-2026-13542) that executes malicious code on install (malicious version 35.5.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in delivery-ci-jira (npm)
What this malware does
On require() of delivery-ci-jira, vendor.js fetches a platform-specific binary from a rotating list of string-split-obfuscated Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev) with a base64-over-DNS TXT fallback via sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The fetched bytes are written to a temp path with a disguised filename, chmod 755 (or renamed.exe on Windows), and spawned detached via cp.spawn("/bin/sh", ["-c", fp + " &"], {detached:true}). Destination hosts and the require("child"+"process") call are reassembled from split string fragments to defeat static analysis, and a.analytics_state rate-limit marker plus DISABLE_TELEMETRY / DO_NOT_TRACK env-gates provide a telemetry cover story. lib/telemetry.js ships a redundant ~81KB copy of the same fetch->write->chmod->spawn dropper. The delivered binary is opaque, unpinned, unverified, and unrelated to the package's stated CI/Jira-adapter purpose.
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-jira (version 35.5.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging delivery-ci-jira across your stack and pipelines.
If you installed it — respond
Remove delivery-ci-jira 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-jira 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-jira 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-jira-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.