What does the cardsmobile-http malware do?

On require of the package, index.js loads _ext.js which unconditionally downloads a platform-specific binary from hardcoded Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT chunked fallback across *.dl.wel1.ru subdomains, writes it to /var/tmp/.cache_ on Unix or %TEMP%\dotnet_diag_ .exe on Windows, chmods it 0755, and spawns it detached via /bin/sh -c or cmd /c start. Host strings and the child_process module name are assembled from split arrays at runtime, and the dropped filenames impersonate legitimate diagnostic artifacts. A sibling module lib/telemetry.js contains a parallel dropper im

Which versions of cardsmobile-http are malicious?

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

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

cardsmobile-http is a typosquat — you almost certainly intended a legitimately-named package. Remove cardsmobile-http, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

If cardsmobile-http 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-http part of a known attack campaign?

Yes — cardsmobile-http is associated with the IN-MAL-2026-015238 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-http 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-http (version 35.3.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cardsmobile-http across your stack and pipelines.

Malicious package

cardsmobile-httpnpm

cardsmobile-http is a confirmed malicious npm package (MAL-2026-12533) that typosquats a legitimate package to trick installs (malicious version 35.3.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cardsmobile-http (npm)

MAL-2026-12533

Immediate action

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

npm uninstall cardsmobile-http

What this malware does

On require of the package, index.js loads ext.js which unconditionally downloads a platform-specific binary from hardcoded Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT chunked fallback across *.dl.wel1.ru subdomains, writes it to /var/tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmods it 0755, and spawns it detached via /bin/sh -c or cmd /c start. Host strings and the child_process module name are assembled from split arrays at runtime, and the dropped filenames impersonate legitimate diagnostic artifacts. A sibling module lib/telemetry.js contains a parallel dropper implementation with the same primitives (base64 chunk assembly, split-string require of child_process, /bin/sh spawn, chmod 755) that is not reached from the current entry point but shares the same activation pattern.

Malicious versions

1 flagged

35.3.3

Indicators of compromise (SHA-256)

1dd23d89483d10aedc3f1a8717673dbae0608df14a168e5d2287e09afe631af7

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cardsmobile-http (version 35.3.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cardsmobile-http across your stack and pipelines.
If you installed it — respond
cardsmobile-http is a typosquat — you almost certainly intended a legitimately-named package. Remove cardsmobile-http, 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 cardsmobile-http 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-http 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-http on npm has been identified as a malicious package (version 35.3.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015238

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cardsmobile-http-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