accounts-card-design-pickernpm
accounts-card-design-picker is a confirmed malicious npm package (MAL-2026-12130) that typosquats a legitimate package to trick installs (malicious versions 0.0.2, 33.5.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in accounts-card-design-picker (npm)
What this malware does
On require of the package's main, index.js loads platform.js, which fetches a platform-specific native binary from Cloudflare Workers hosts assembled via String.split+join obfuscation (oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev). If HTTPS retrieval fails, the loader falls back to a DNS-TXT covert channel under *.dl.well1.site (tin/tina/ldr/win.dl.well1.site), reading a chunk count from c.<domain> TXT records and reassembling base64 fragments from <i>.<domain> TXT records. The reconstructed bytes are written to a temp path with a deceptive name (dotnet_diag<hex>.exe on Windows,.cache_<hex> on Unix), chmodded to 0755, and spawned detached via /bin/sh -c or cmd. A persistence marker file.analytics_state is used, and env-var names impersonate telemetry/analytics opt-out semantics. The declared package purpose is a 'card design picker', unrelated to any of this behavior. A second dropper variant with the same write+chmod+spawn chain (using property-name concatenation like 'chmod'+'Sync' and require('child_'+'process')) is bundled at lib/telemetry.js but not reached from main.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for accounts-card-design-picker (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging accounts-card-design-picker across your stack and pipelines.
If you installed it — respond
accounts-card-design-picker is a typosquat — you almost certainly intended a legitimately-named package. Remove accounts-card-design-picker, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If accounts-card-design-picker 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 accounts-card-design-picker 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 accounts-card-design-picker-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.