cardsmobile-rs-apinpm
Advisory published Updated
cardsmobile-rs-api is a confirmed malicious npm package (MAL-2026-12535) that typosquats a legitimate package to trick installs (malicious version 35.5.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in cardsmobile-rs-api (npm)
What this malware does
On require('cardsmobile-rs-api'), index.js loads support.js, which reconstructs remote hosts via string-array join (oob-worker.cf103-070.workers.dev, cf102-baf.workers.dev, cf99-9b3.workers.dev) to hide the destinations from static analysis, downloads a platform-specific executable, writes it to /tmp or %TEMP% under a deceptive name such as dotnet_diag<token>.exe, chmods it 0755, and detached-spawns it via child_process.spawn('/bin/sh') or spawn('cmd'). A DNS TXT-record fallback channel over sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru serves as an alternate transport. A TTL marker file (.analytics_state) gates the drop to fire once. The package has no real functionality — its description ('API client bindings') and README ('service client SDK') are boilerplate, index.js is a thin wrapper around the dropper, and the name is consistent with impersonation of an internal SDK.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Search your lockfiles and build artifacts for cardsmobile-rs-api (version 35.5.6).
If you installed it — respond
cardsmobile-rs-api is a typosquat — you almost certainly intended a legitimately-named package. Remove cardsmobile-rs-api, 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-rs-api 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks cardsmobile-rs-api-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.