# MAL-2026-12070: Malicious code in shopping-shared-atom-mobile-cart-counter (npm)


- **Type:** Malicious package
- **Package:** `shopping-shared-atom-mobile-cart-counter` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-63p3-ggxm-fcwg

## What is MAL-2026-12070?

MAL-2026-12070 is a malicious package in shopping-shared-atom-mobile-cart-counter, published on 5 Aug 2026. 

### Official description

shopping-shared-atom-mobile-cart-counter@20.6.6 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.

## What should I do about MAL-2026-12070?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-12070 is a malicious package: shopping-shared-atom-mobile-cart-counter (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-12070/ (Markdown: https://insights.sbomify.com/MAL-2026-12070/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-12070

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-12070/
Summaries are generated and may contain mistakes; the official description above is the record.