NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

cardsmobile-cardsmobile-corenpm

Advisory published Updated

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

Malicious code in cardsmobile-cardsmobile-core (npm)

MAL-2026-12529
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall cardsmobile-cardsmobile-core

What this malware does

On require() of cardsmobile-cardsmobile-core, index.js loads shim.js which selects a platform-specific payload path, fetches an unsigned executable from attacker-controlled Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS TXT chunked-base64 fallback via sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru, writes it to a hidden path under /var/tmp or %TEMP% with decoy names (dotnet_diag.exe,.cache_), chmods 0755, and spawns it detached via /bin/sh or cmd.exe. A cooldown lockfile at /tmp/.analytics_state prevents re-runs. Endpoint hostnames and dangerous API names are assembled at runtime via.join('') from string fragments (e.g. require("child_" + "process"), fs["chmod" + "Sync"]) to evade static analysis, and lib/telemetry.js additionally decodes a base64 payload before executing it. A DISABLE_TELEMETRY environment check is present but does not gate the dropper. Loading this package grants remote code execution on the installer's host with detached persistence beyond the Node process.

Malicious versions

1 flagged
35.6.6

Indicators of compromise (SHA-256)

657552d9de3cceb4fd25921aea0f1470d8c6f70af574242b4d3e4273367e2d30

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for cardsmobile-cardsmobile-core (version 35.6.6).

  2. If you installed it — respond

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

  3. Did it already run?

    If cardsmobile-cardsmobile-core was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-015239

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

cardsmobile-cardsmobile-core (npm) malicious package — MAL-2026-12529 | O3 Security