Which versions of lint-prettier are malicious?

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

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

Remove lint-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 lint-prettier — how do I know if it already compromised me?

If lint-prettier was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is lint-prettier part of a known attack campaign?

Yes — lint-prettier is associated with the RLMA-2026-05141, RLUA-2026-06307 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 lint-prettier across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for lint-prettier (version 1.0.4).

Malicious package

lint-prettiernpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

Malicious code in lint-prettier (npm)

MAL-2026-7312

Immediate action

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

npm uninstall lint-prettier

Malicious versions

1 flagged

1.0.4

Indicators of compromise (SHA-256)

d54e54aa48b19935fa0ba510ce15bc48419cc3c426a97f924c980082b4cabaf5

0f110d49038a790e4ff4be0fe2d0180ea68e26bd3631319a31c2c91a4b88d0ec

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for lint-prettier (version 1.0.4).
If you installed it — respond
Remove lint-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 lint-prettier was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. lint-prettier on npm has been identified as a malicious package (version 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05141RLUA-2026-06307

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks lint-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