Block malicious npm packages before they install.
LPM Firewall checks package versions and transitive dependencies against live malware intelligence, AI review, and product-security policy blocks. Blocked package versions are stopped before they ever reach your machine.
Latest blocked packages.
The newest package versions blocked by the firewall, including malware, data exfiltration, remote code execution, and AI-agent control-surface risks.
OpenSSF Malicious Packages via OSV confirms dzyclutch-baileys@1.1.23 as malicious (MAL-2026-17620): Malicious code in dzyclutch-baileys (npm)
OpenSSF Malicious Packages via OSV confirms dzyclutch-baileys@1.1.22 as malicious (MAL-2026-17620): Malicious code in dzyclutch-baileys (npm)
OpenSSF Malicious Packages via OSV confirms dzyclutch-baileys@1.1.21 as malicious (MAL-2026-17620): Malicious code in dzyclutch-baileys (npm)
OpenSSF Malicious Packages via OSV confirms dzyclutch-baileys@1.1.20 as malicious (MAL-2026-17620): Malicious code in dzyclutch-baileys (npm)
OpenSSF Malicious Packages via OSV confirms dzyclutch-baileys@1.1.19 as malicious (MAL-2026-17620): Malicious code in dzyclutch-baileys (npm)
OpenSSF Malicious Packages via OSV confirms dzyclutch-baileys@1.1.18 as malicious (MAL-2026-17620): Malicious code in dzyclutch-baileys (npm)
OpenSSF Malicious Packages via OSV confirms dzyclutch-baileys@1.1.17 as malicious (MAL-2026-17620): Malicious code in dzyclutch-baileys (npm)
OpenSSF Malicious Packages via OSV confirms dzyclutch-baileys@1.1.15 as malicious (MAL-2026-17620): Malicious code in dzyclutch-baileys (npm)
OpenSSF Malicious Packages via OSV confirms dzyclutch-baileys@14.0.0 as malicious (MAL-2026-17620): Malicious code in dzyclutch-baileys (npm)
Turn on Firewall through LPM.
Start with LPM CLI, become Pro on lpm.dev, then enable Firewall from lpm config. Your package installs keep the speed of LPM with an extra package-version block layer in front.
Install LPM CLI from cli.lpm.dev. It is already faster and more secure for npm installs, even before Firewall is enabled.
Upgrade on lpm.dev so your account can use LPM Firewall protection across package installs.
Open LPM CLI, enable Firewall from lpm config, and route package installs through the protected registry.
Start with LPM CLI, then enable Firewall.
Install the faster and more secure CLI, upgrade to Pro on lpm.dev, and enable Firewall from lpm config when you are ready.