Which versions of cardsmobile-notifications are malicious?

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

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

cardsmobile-notifications establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

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

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

Malicious package

cardsmobile-notificationsnpm

cardsmobile-notifications is a confirmed malicious npm package (MAL-2026-12534) that opens a backdoor for remote access (malicious version 35.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cardsmobile-notifications (npm)

MAL-2026-12534

Immediate action

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

npm uninstall cardsmobile-notifications

What this malware does

On require() of cardsmobile-notifications, index.js loads support.js which fetches an OS/arch-specific executable from a rotating list of obfuscated Cloudflare Workers endpoints (oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev), with a DNS TXT covert-channel fallback that assembles a base64 payload from numbered subdomains under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The downloaded bytes are written to /var/tmp or %TEMP% under disguised names (dotnet_diag.exe,.cache_), chmod 0755, and spawned detached via cp.spawn("/bin/sh", ["-c", fp + " &"], {detached:true}).unref(). No hash or signature verification is performed; the destinations are not the publisher; the C2 hostnames are assembled via string-split.join("") to evade static matching. A second 81KB module lib/telemetry.js, disguised as an APM/telemetry SDK, contains the same base64-decode + chmod 0755 + /bin/sh spawn pattern; it is not reached from index.js in this version but is armed and could be re-wired by a future release.

Malicious versions

1 flagged

35.7.6

Indicators of compromise (SHA-256)

5a75c5659b227cbea7e622e9c5613594e590fae0580db08420e9f2493b2fd3d2

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cardsmobile-notifications (version 35.7.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cardsmobile-notifications across your stack and pipelines.
If you installed it — respond
cardsmobile-notifications establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If cardsmobile-notifications 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-notifications 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-notifications on npm has been identified as a malicious package (version 35.7.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015234

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cardsmobile-notifications-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database