Which versions of prettier_v2 are malicious?

The following npm versions of prettier_v2 are flagged malicious: 3.8.5. Treat any of these as compromised.

How do I remediate prettier_v2 if I installed it?

prettier_v2 is a typosquat — you almost certainly intended a legitimately-named package. Remove prettier_v2, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed prettier_v2 — how do I know if it already compromised me?

If prettier_v2 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.

Is prettier_v2 part of a known attack campaign?

Yes — prettier_v2 is associated with the GHSA-cmfj-34j9-8w66, IN-MAL-2026-009432, RLMA-2026-05597 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find prettier_v2 across my projects, lockfiles, and CI pipelines?

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

Malicious package

prettier_v2npm

prettier_v2 is a confirmed malicious npm package (MAL-2026-5846) that typosquats a legitimate package to trick installs (malicious version 3.8.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in prettier_v2 (npm)

MAL-2026-5846

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall prettier_v2

What this malware does

Package name 'prettier_v2' closely resembles the widely-used 'prettier' formatter package, raising typosquat concerns. The file lib/mirror.js contains a Buffer.from(..., 'base64').toString('utf8') decode pattern, which is commonly used to hide payload strings or code. Without confirmation of how the decoded content is used (data vs. eval/exec), intent cannot be conclusively determined, but the combination of a confusable package name and obfuscated string handling warrants human review before installation.

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

1 flagged

3.8.5

Indicators of compromise (SHA-256)

b0da6eb947f9a9046563fe43e0b5064d7dc2a75e019425a564276d44d39bc263

52d6c46e6d7e7ba0269dbb3d9725b5943d1b4b94ac2587a5738983cb93d8e1cf

34e10e35ed57d7d7e1adc4c93dbf2c530d5d78261f9b9a0bfab5f2e831622d33

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for prettier_v2 (version 3.8.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging prettier_v2 across your stack and pipelines.
If you installed it — respond
prettier_v2 is a typosquat — you almost certainly intended a legitimately-named package. Remove prettier_v2, 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 prettier_v2 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 prettier_v2 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. prettier_v2 on npm has been identified as a malicious package (version 3.8.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-cmfj-34j9-8w66IN-MAL-2026-009432RLMA-2026-05597

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks prettier_v2-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database