npm detections from LPM Firewall.

The source establishes a concrete, default credential-exfiltration path to a third-party endpoint during ordinary package use. No install hook is needed for this runtime behavior to be ma...

The source contains an unconditional import-time remote-code loader. This is concrete malicious behavior, irrespective of the lack of lifecycle hooks.

The package contains a concrete postinstall dependency-injection chain against the installer project's package.json. No benign package function or user-invoked setup path justifies this m...

The install-time hook deliberately mutates the invoking project by adding an unrelated package. This is concrete unconsented staged-package installation behavior.

The install hook performs an undeclared, project-root package installation, a concrete staged-payload mechanism. No benign package functionality or source explains this behavior.

This is concrete, unconsented install-time remote code execution, not merely a user-invoked downloader. Platform and global-install guards reduce reach but do not remove the attack surface.

The manifest contains a concrete install-time supply-chain action outside its own package directory, with no package functionality to justify it. This is malicious installation behavior r...

The explicit preinstall hook performs an unconsented secondary package installation. This is concrete install-hook abuse even though the package itself contains no direct exfiltration or...

The manifest contains a concrete, unconsented install-time second-stage package installation outside its own directory. This is a dependency-injection payload chain, not a package-aligned...

This is a concrete install-time remote payload chain designed to evade platform download-security controls, not a benign library dependency. The bundled checksum does not mitigate the pac...

The import-time payload is intentionally concealed and combines networking with execSync/spawn and filesystem access. No lifecycle hook is needed because ordinary package import activates...

The package contains a concrete, remote-controlled and unconsented action against users' WhatsApp accounts during ordinary runtime. Its install hook is benign, but does not mitigate the r...

Confirmed source establishes a reachable obfuscated remote payload loader with eval and detached process execution. Absence of an npm lifecycle hook does not mitigate runtime execution on...

The runtime entrypoint contains an unconditional remote payload fetch-and-execute chain, which is concrete malicious behavior. The declared arbitrary command MCP tool adds a separate host...

This is a concrete unconsented postinstall mutation of broad, foreign AI-agent control surfaces, including automatic approval and tool interception. No network exfiltration is needed for...

The lifecycle hook concretely modifies consumer AI-agent and Git control paths, rather than merely exposing an explicit setup command. No exfiltration was found, but the unconsented posti...

Direct source inspection confirms automatic transmission of runtime environment secrets to a fixed external endpoint. The lack of install-time execution does not remove the concrete crede...

The source implements an authenticated upload of environment-derived secret values to a hard-coded external host. No install hook exists, but the runtime data flow is concrete and unsafe.

The published CommonJS entrypoint contains a concealed, hash-gated payload launcher with detached child-process execution. The lack of lifecycle hooks does not mitigate runtime execution...

The import-time IP-harvesting and Slack submission chain is directly present in package source and reachable through an exported entrypoint. This is malicious behavior despite the absence...