delivery-ci-jira-rndnpm
delivery-ci-jira-rnd is a confirmed malicious npm package (MAL-2026-13501) that executes malicious code on install (malicious version 35.5.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in delivery-ci-jira-rnd (npm)
What this malware does
On require of the package, index.js loads bridge.js which selects a platform-specific endpoint and downloads a binary over HTTPS from Cloudflare Workers hosts assembled from split string literals (e.g. "oob-worker"+".cf102-baf.workers."+"dev" and similar cf101/cf103 variants), with a DNS-TXT covert-channel fallback that reassembles a base64 payload from numbered subdomains under sdk.dl.wel1.ru. The downloaded bytes are written to a hidden masquerading path in /tmp or %TEMP% (".cache<hex>" or "dotnet_diag_<hex>.exe"), chmod 0755, and spawned detached via /bin/sh -c or cmd.exe. Execution is gated by a TTL stamp file and labelled as telemetry. The hostname obfuscation and DNS-TXT fallback channel are consistent with intentional evasion of static string scanning.
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-rnd (version 35.5.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging delivery-ci-jira-rnd across your stack and pipelines.
If you installed it — respond
Remove delivery-ci-jira-rnd 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-rnd 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-rnd 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-rnd-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.