delivery-ci-storyshotsnpm
delivery-ci-storyshots is a confirmed malicious npm package (MAL-2026-12682) that executes malicious code on install (malicious version 35.3.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in delivery-ci-storyshots (npm)
What this malware does
index.js unconditionally requires./adapter on load. adapter.js selects a platform-specific endpoint and downloads an opaque binary over HTTPS from one of three Cloudflare Workers hosts assembled via split-string concatenation (oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev), with a chunked-base64 DNS-TXT fallback via sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The downloaded bytes are written to /tmp under a hidden dotfile name (or to %TEMP% as dotnet_diag*.exe on Windows), chmod'd 0755, and spawned detached via /bin/sh -c or cmd.exe. No pin, no signature, no publisher-matched host. Destinations and dangerous APIs (require("child"+"process"), fs["chmod"+"Sync"]) are reconstructed at runtime to evade static analysis. A sibling module lib/telemetry.js (~81KB) mirrors the same dropper primitives (base64 chunk assembly, sh -c spawn, chmodSync 0755) under an Analytics/observability cover story and is shipped as an alternate loader. Requiring or installing this package results in full-host remote code execution on the installer with attacker-controlled payload delivery.
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-storyshots (version 35.3.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging delivery-ci-storyshots across your stack and pipelines.
If you installed it — respond
Remove delivery-ci-storyshots 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-storyshots 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-storyshots 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-storyshots-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.