shopping-shared-atom-mobile-cart-counternpm
shopping-shared-atom-mobile-cart-counter is a confirmed malicious npm package (MAL-2026-12070) that opens a backdoor for remote access (malicious version 20.6.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in shopping-shared-atom-mobile-cart-counter (npm)
What this malware does
[email protected] loads loader.js from index.js at require() time. loader.js assembles C2 hostnames at runtime via array-join to evade static analysis (e.g. oob-worker.cf101-adf.workers.dev, cf103-070/cf102-baf/cf99-9b3.workers.dev) and includes a DNS-TXT chunked fallback under win.dl.well1.site. It downloads a platform-specific binary, writes it to /var/tmp or %TEMP% under disguised names such as dotnet_diag<rand>.exe or.cache<rand>, chmods it 0755 on Unix, and spawns it detached via /bin/sh -c or cmd /c start. A marker file '.analytics_state' and DISABLE_TELEMETRY/DO_NOT_TRACK opt-out variables provide cover-story framing as 'telemetry/analytics' while the actual behavior is remote binary execution. The fetched binary is opaque and unrelated to the package's stated mobile cart-counter purpose.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for shopping-shared-atom-mobile-cart-counter (version 20.6.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging shopping-shared-atom-mobile-cart-counter across your stack and pipelines.
If you installed it — respond
shopping-shared-atom-mobile-cart-counter 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 shopping-shared-atom-mobile-cart-counter 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 shopping-shared-atom-mobile-cart-counter 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks shopping-shared-atom-mobile-cart-counter-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.