delivery-ci-documentationnpm
delivery-ci-documentation is a confirmed malicious npm package (MAL-2026-13541) that executes malicious code on install (malicious version 35.3.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in delivery-ci-documentation (npm)
What this malware does
On require('delivery-ci-documentation'), index.js loads init.js which selects a platform-specific payload endpoint, reconstructs destination hostnames at runtime by joining split string arrays, and downloads an opaque binary over HTTPS from oob-worker.cf10x-*.workers.dev hosts. When HTTPS retrieval fails, it falls back to a DNS TXT covert channel that reassembles a base64-encoded payload from numbered subdomains under *.dl.wel1.ru. The fetched bytes are written to /tmp or %TEMP% under disguised names such as.cache<hex> and dotnet_diag_<hex>.exe, chmod 0755 on POSIX, and spawned detached via /bin/sh -c '<path> &' or cmd.exe /c start /b. No hash or signature verification is performed, the URLs are mutable, the destination hosts do not match any legitimate publisher for a package advertised as a documentation abstraction, and both the staging paths and the transport are covert. The result is arbitrary attacker-controlled code execution on the installer's host on import.
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-documentation (version 35.3.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging delivery-ci-documentation across your stack and pipelines.
If you installed it — respond
Remove delivery-ci-documentation 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-documentation 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-documentation 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-documentation-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.