Which versions of cardsmobile-storage are malicious?

The following npm versions of cardsmobile-storage are flagged malicious: 35.6.5. Treat any of these as compromised.

How do I remediate cardsmobile-storage if I installed it?

Remove cardsmobile-storage 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.

I already installed cardsmobile-storage — how do I know if it already compromised me?

If cardsmobile-storage 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.

Is cardsmobile-storage part of a known attack campaign?

Yes — cardsmobile-storage is associated with the IN-MAL-2026-015236 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find cardsmobile-storage across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cardsmobile-storage (version 35.6.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cardsmobile-storage across your stack and pipelines.

Malicious package

cardsmobile-storagenpm

cardsmobile-storage is a confirmed malicious npm package (MAL-2026-12536) that executes malicious code on install (malicious version 35.6.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cardsmobile-storage (npm)

MAL-2026-12536

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall cardsmobile-storage

What this malware does

On require(), index.js loads shim.js which selects a platform-specific payload URL from a string-split-obfuscated list of Cloudflare Workers subdomains (oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev), with a DNS-TXT chunked fallback via sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The downloaded binary is written to /tmp or %TEMP% under a disguised name (.cache<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), chmod 0755 is applied on POSIX, and the file is spawned detached and unref'd via /bin/sh -c or cmd.exe/start. Host names and the child_process module name are assembled at runtime from split-string arrays (require("child_" + "process"), ["oob-worke","r.cf99-9b3",".wor","kers.d","ev"].join("")) to evade static URL/module scanners. A parallel dropper implementation with the same primitives (HTTPS with endpoint rotation, DNS-TXT base64 service discovery, fs.chmodSync 0o755, cp.spawn("/bin/sh", ["-c", filePath + " &"])) is bundled in lib/telemetry.js (81 KB, labeled as an "Analytics SDK") and shipped in the tarball as an alternate execution path.

Malicious versions

1 flagged

35.6.5

Indicators of compromise (SHA-256)

c9d80bf756b4d7e7f6e27afd68a796dc43ca50d28e692d11b4af141b0af5235b

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cardsmobile-storage (version 35.6.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cardsmobile-storage across your stack and pipelines.
If you installed it — respond
Remove cardsmobile-storage 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-storage 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-storage 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

No. cardsmobile-storage on npm has been identified as a malicious package (version 35.6.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015236

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cardsmobile-storage-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database