Which versions of cardsmobile-event-emitter are malicious?

The following npm versions of cardsmobile-event-emitter are flagged malicious: 35.2.8. Treat any of these as compromised.

How do I remediate cardsmobile-event-emitter if I installed it?

Remove cardsmobile-event-emitter 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-event-emitter — how do I know if it already compromised me?

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

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

Malicious package

cardsmobile-event-emitternpm

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

Malicious code in cardsmobile-event-emitter (npm)

MAL-2026-12532

Immediate action

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

npm uninstall cardsmobile-event-emitter

What this malware does

On require of cardsmobile-event-emitter, index.js unconditionally loads loader.js, which fetches an opaque platform-specific binary over HTTPS from runtime-concatenated Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS TXT fallback channel across sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched bytes are written to /tmp (Unix) or %TEMP% (Windows) under a disguised name such as.cache<hex> or dotnet_diag_<hex>.exe, chmod 0755'd, and spawned detached via /bin/sh -c or cmd /c start /b. Destination hostnames are assembled via array-join string splits to evade static analysis, and the DNS-TXT channel reassembles base64-encoded TXT records into an alternate payload path. The package's stated 'event emitter' purpose is unrelated to the download-and-execute behavior; there is no version pinning and no hash or signature verification of the fetched binary. A second full copy of the dropper (lib/telemetry.js, ~81KB) ships in the tarball with the same fetch/spawn shape.

Malicious versions

1 flagged

35.2.8

Indicators of compromise (SHA-256)

66db77fd91ad9316ea06a13f10281595e60cf846e89787bcbb793d061cdd1315

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-event-emitter (version 35.2.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cardsmobile-event-emitter across your stack and pipelines.
If you installed it — respond
Remove cardsmobile-event-emitter 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-event-emitter 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-event-emitter 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-event-emitter on npm has been identified as a malicious package (version 35.2.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015235

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cardsmobile-event-emitter-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