Which versions of prettier-lint-lenz are malicious?

The following npm versions of prettier-lint-lenz are flagged malicious: 1.0.0, 2.6.4. Treat any of these as compromised.

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

prettier-lint-lenz is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

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

Yes — prettier-lint-lenz is associated with the IN-MAL-2026-002706, IN-MAL-2026-002707 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-lint-lenz 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-lint-lenz (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging prettier-lint-lenz across your stack and pipelines.

Malicious package

prettier-lint-lenznpm

Malicious code in prettier-lint-lenz (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3769

Immediate action

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

npm uninstall prettier-lint-lenz

What this malware does

Package impersonates the popular prettier formatter — README and description are copied verbatim from the real Prettier project, but the package ships no formatter code. Instead, package.json declares "postinstall": "node index.mjs", which on Windows POSTs an install beacon to a hardcoded bare-IP C2 (http://204.10.194.64:5000/api/nonce), copies a bundled prettier-lint/ directory to %LOCALAPPDATA%\prettier-lint, and executes ctll.mjs from the deployed location. ctll.mjs writes a hidden VBScript runner and registers a Windows Scheduled Task named CdllProtect with a LogonTrigger (schtasks /Create /XML) that relaunches cdll.mjs via wscript.exe //nologo in a hidden window on every user logon, with 999 retries and no execution time limit. The deployed cdll.mjs polls the clipboard every ~250ms via powershell.exe Get-Clipboard -Raw and POSTs the raw clipboard text as JSON to the same hardcoded endpoint over plain HTTP on every change, exfiltrating passwords, 2FA codes, wallet addresses, and any copied text. All three components (install-time beacon, deployed worker, persistence) share the attacker-controlled endpoint 204.10.194.64:5000.

Malicious versions

2 flagged

1.0.02.6.4

Indicators of compromise (SHA-256)

28f7035dda69170600724a31f4b3543e02ac23c9153f3a62c35f2ee5264eef44

81348c27286005b3399de72570527ed0afc1414830a74fae852229bcfda31e01

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for prettier-lint-lenz (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging prettier-lint-lenz across your stack and pipelines.
If you installed it — respond
prettier-lint-lenz is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If prettier-lint-lenz 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-lint-lenz 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-lint-lenz on npm has been identified as a malicious package (versions 1.0.0, 2.6.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-002706IN-MAL-2026-002707

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks prettier-lint-lenz-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring