Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

peter-desktop-peter-big-columnnpm

peter-desktop-peter-big-column is a confirmed malicious npm package (MAL-2026-12184) that executes malicious code on install (malicious version 20.3.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in peter-desktop-peter-big-column (npm)

MAL-2026-12184
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall peter-desktop-peter-big-column

What this malware does

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.

Malicious versions

1 flagged
20.3.2

Indicators of compromise (SHA-256)

7593cd2f0f03765e6debc06626ee5d771a32e0d7eb579ddca1bfc5ca53bc22e6

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for peter-desktop-peter-big-column (version 20.3.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging peter-desktop-peter-big-column across your stack and pipelines.

  2. If you installed it — respond

    Remove peter-desktop-peter-big-column 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.

  3. Did it already run?

    If peter-desktop-peter-big-column 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.

  4. How O3 protects you

    O3 blocks peter-desktop-peter-big-column 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. peter-desktop-peter-big-column on npm has been identified as a malicious package (version 20.3.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014475

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks peter-desktop-peter-big-column-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.

Explore