# MAL-2026-12184: Malicious code in peter-desktop-peter-big-column (npm)


- **Type:** Malicious package
- **Package:** `peter-desktop-peter-big-column` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-6jpg-pv9h-2rf5

## What is MAL-2026-12184?

MAL-2026-12184 is a malicious package in peter-desktop-peter-big-column, published on 5 Aug 2026. 

### Official description

On require(), index.js loads _runtime.js which assembles download hostnames at runtime from split string fragments (resolving to oob-worker.cf99-9b3.workers.dev and *.dl.well1.site) and fetches a platform-specific binary via HTTPS with a DNS TXT fallback channel. The retrieved bytes are written to /tmp or %TEMP% under a disguised name (.cache_<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), chmod 0755 is applied on POSIX, and the binary is spawned detached via /bin/sh -c '<path> &' or cmd /c start. A deduplication lockfile is disguised as an analytics stamp. lib/telemetry.js ships a second copy of the same fetch-write-chmod-spawn dropper under an 'apm.node' SDK guise. The delivered binary is attacker-controlled and opaque; string-array hostname assembly hides the destinations from static inspection.

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-12184?

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-12184 is a malicious package: peter-desktop-peter-big-column (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-12184/ (Markdown: https://insights.sbomify.com/MAL-2026-12184/index.md)
```

## Sources

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

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