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. In enforce mode, blocked package versions are stopped before they ever reach your machine.

Threat feed

Latest blocked packages.

The latest blocked version per package, including malware, data exfiltration, and remote code execution.

Full advisory archive
anyray-connect
Policy · Credential sent to publisher

The managed integration sends an Anthropic credential to the gateway’s own optimization endpoint.

v0.11.7371 min ago
@pisell/pisellos
Data exfiltration

The default ScanOrder path routes runtime logs, including application context and serialized error details, to hard-coded Feishu bot webhooks.

v2.3.2215 mins ago
@adaptiqai/mcp
Policy · Credential sent to publisher

The package conditionally takes an Anthropic environment credential and makes it available as a Bearer credential for requests to the AdaptiqAI API.

v0.1.128 mins ago
pcm-shared-components
Protestware

The package installs styled-components, whose postinstall hook targets Russian-locale environments with an unrelated political message.

v2.1.56016 mins ago
crysk
Policy · Credential sent to publisher

The platform workflow sends a GitHub-issued OIDC credential to the publisher's API, which exchanges it for a GitHub installation token.

v0.12.021 mins ago
propr-cli
Policy · Credential sent to publisher

The default ProPR Connect setup path sends a GitHub credential to the vendor-run relay, while its prompt does not disclose that transfer.

v0.9.329 mins ago
diavola
Policy · Unreviewed code

The earlier review correctly identified a reachable update-and-execute path: invoking the CLI can replace and run the latest release binary.

v0.2.1346 mins ago
@obsrviq/system
Policy · Unreviewed code

The default-running agent accepts server-returned upgrade commands and installs a server-selected release of itself from npm, then restarts its service.

v0.11.1546 mins ago
@zervonex/baileys
Malware

The package automatically uses the connected WhatsApp account to follow two publisher-selected newsletters, with retries, unless the user knows to disable the setting.

v4.0.5-final47 mins ago
Get started

Turn on Firewall through LPM.

Start with LPM CLI, become Pro on lpm.dev, then turn on Firewall with lpm config. Packages still download from the npm registry, and LPM CLI looks up their verdicts in a separate request.

  1. Install LPM CLI

    Install LPM CLI from cli.lpm.dev. It is already faster and more secure for npm installs, even before Firewall is enabled.

  2. Become Pro

    Upgrade on lpm.dev so your account can use LPM Firewall protection across package installs.

  3. Enable Firewall

    Turn on Firewall with lpm config. Start in monitor mode to see what it would block, then switch to enforce mode to stop blocked versions before they reach your machine.

Every install, checked.

With Firewall on, LPM CLI looks up the verdict of each public npm version it installs, transitive dependencies included. In enforce mode, it waits for each verdict and stops blocked versions before they reach your machine.