tinkoff-codeceptjs-storyshots-alphanpm
tinkoff-codeceptjs-storyshots-alpha is a confirmed malicious npm package (MAL-2026-12237) that steals credentials and exfiltrates sensitive data (malicious version 20.8.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tinkoff-codeceptjs-storyshots-alpha (npm)
What this malware does
The package's index.js unconditionally requires bootstrap.js on load. bootstrap.js selects a platform-specific path (linux_x64, linux_arm64, darwin, win32), fetches an opaque binary from Cloudflare Workers hosts under oob-worker.cf10*.workers.dev whose names are reassembled at runtime via array-join to evade static inspection, and includes a DNS TXT chunked fallback channel using tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site. The downloaded bytes are written to /tmp or %TEMP% under disguised names such as dotnet_diag<hex>.exe and.cache<hex>, chmod 0755 on unix, and spawned detached via spawn("/bin/sh", ["-c", path + " &"]).unref() (spawn("cmd",...) on Windows). A marker file named.analytics_state gates repeat execution on a ~22374 second cooldown, and opt-out environment variables are honored in a way that mimics legitimate telemetry. A secondary module lib/telemetry.js contains the same dropper primitives with property-name obfuscation (fs["chmod"+"Sync"], require("child_"+"process"), Buffer.from(chunks,"base64")) alongside spawn("/bin/sh", ["-c", filePath + " &"]). The name tinkoff-codeceptjs-storyshots-alpha impersonates a well-known corporate scope; there is no legitimate reason for a storyshots testing helper to fetch and execute an opaque native binary from an anonymous Cloudflare Workers host at import time.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tinkoff-codeceptjs-storyshots-alpha (version 20.8.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tinkoff-codeceptjs-storyshots-alpha across your stack and pipelines.
If you installed it — respond
tinkoff-codeceptjs-storyshots-alpha is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If tinkoff-codeceptjs-storyshots-alpha 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 tinkoff-codeceptjs-storyshots-alpha 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 tinkoff-codeceptjs-storyshots-alpha-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.