Which versions of test-prettier are malicious?

The following npm versions of test-prettier are flagged malicious: 1.0.9. Treat any of these as compromised.

How do I remediate test-prettier if I installed it?

Remove test-prettier 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.

I already installed test-prettier — how do I know if it already compromised me?

If test-prettier 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 test-prettier part of a known attack campaign?

Yes — test-prettier is associated with the GHSA-6h3j-xcmr-vmwx 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 test-prettier 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 test-prettier (version 1.0.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test-prettier across your stack and pipelines.

Malicious package

test-prettiernpm

test-prettier is a confirmed malicious npm package (MAL-2026-6893) that executes malicious code on install (malicious version 1.0.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in test-prettier (npm)

MAL-2026-6893

Immediate action

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

npm uninstall test-prettier

What this malware does

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

1.0.9

Indicators of compromise (SHA-256)

2e81aaf3ca98b6be66b1dd1e6c1c2de4d9487b31d82e74d6c8283b9d9d5a8ee2

Detection & response playbook

Malicious package

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

Campaign

GHSA-6h3j-xcmr-vmwx

References

github.com

Detect & block this

O3 blocks test-prettier-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