cardsmobile-collectionnpm
cardsmobile-collection is a confirmed malicious npm package (MAL-2026-12346) that executes malicious code on install (malicious version 20.4.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in cardsmobile-collection (npm)
What this malware does
On require() of the package,./runtime.js runs a top-level setup() that downloads a platform-specific binary from string-concatenated hostnames (oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS-TXT fallback that reconstructs the payload from base64 TXT records served by tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site. The fetched bytes are written to /var/tmp/.cache<hex> on Unix or %TEMP%/dotnet_diag_<hex>.exe on Windows, chmodded 0755, and spawned detached via child_process (spawn('/bin/sh',...) / spawn('cmd',...)). Destination hosts and the child_process module name are assembled at runtime via array-join concatenation (['tin.dl.well','1.site'].join(''); require('child_'+'process')) to evade static analysis, and the code frames itself as 'analytics' with DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK cover-story env-var checks. A sibling module lib/telemetry.js ships the same fetch-write-chmod-spawn primitives as a dormant duplicate. The dropped binary is opaque and unrelated to the package's stated 'native bridge' purpose; the fetched hostnames are not the package's publisher infrastructure.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
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 cardsmobile-collection (version 20.4.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cardsmobile-collection across your stack and pipelines.
If you installed it — respond
Remove cardsmobile-collection 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 cardsmobile-collection 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 cardsmobile-collection 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 cardsmobile-collection-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.