Malicious code in delivery-ci-jira (npm)
The npm package delivery-ci-jira contained malicious code that fetches and executes platform-specific binaries from attacker-controlled infrastructure on require(). The package was identified by OpenSSF and published as a confirmed malicious package.
- Disclosed
- Last updated
- Blast radius
- Any npm consumer of delivery-ci-jira package
- Ecosystems
- Attack vectors
- Affected entities
- delivery-ci-jiranpm package containing malicious dropper code
The npm package delivery-ci-jira was found to contain malicious code designed to execute arbitrary binaries upon module import. When the package is required, the _vendor.js file initiates a multi-stage dropper that fetches platform-specific binaries from rotating 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 fallback mechanism using domains under wel1.ru.
The fetched binary is written to a temporary file with an obfuscated filename, given execute permissions (chmod 755 on Unix, renamed.exe on Windows), and spawned as a detached process. The malicious code uses string fragmentation and obfuscation techniques to defeat static analysis, including splitting the child_process require statement and using environment variable gates (DISABLE_TELEMETRY, DO_NOT_TRACK) as a cover story for telemetry collection.
A redundant copy of the dropper logic (~81KB) is also present in lib/telemetry.js. The delivered binary is completely opaque, unverified, and unrelated to the package's stated purpose as a CI/Jira adapter. The incident was identified and credited to the OpenSSF malicious packages project.
Indicators of compromise
- Packages
- delivery-ci-jira
- Domains
- oob-worker.cf102-baf.workers.dev
- oob-worker.cf100-416.workers.dev
- oob-worker.cf101-adf.workers.dev
- oob-worker.cf99-9b3.workers.dev
- sdk.dl.wel1.ru
- ext.dl.wel1.ru
- pkg.dl.wel1.ru
- net.dl.wel1.ru
Remediation
- Immediately remove delivery-ci-jira from all projects and dependencies
- Audit npm package.json and lock files for any presence of delivery-ci-jira
- Review execution logs and process history on systems where this package may have been installed
- Check for unexpected outbound connections to Cloudflare Workers domains or wel1.ru subdomains
- Regenerate any credentials or secrets that may have been exposed on affected systems
- Update to a clean, verified alternative for CI/Jira integration if needed
Sources
- GitHub Advisory GHSA-4xf5-gwm6-3rfw · GitHub Advisory Database
Cite this entry
"Malicious code in delivery-ci-jira (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 7, 2026; last updated August 7, 2026. https://supplychainattack.org/incident/malicious-code-in-delivery-ci-jira-npm-1x1waw
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in svelte-dim-kit
The npm package svelte-dim-kit was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and secrets/keys rotated immediately from a different computer.
npmCompromised package - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in stillm4ddpocs-rtest-bravo (npm)
The npm package stillm4ddpocs-rtest-bravo contained malicious code in its preinstall script that automatically executed during installation, collecting system information and internal package metadata and exfiltrating it to a third-party Interactsh collector via HTTPS and DNS tunneling.
npmCompromised package