npm detections from LPM Firewall.

The package is a staged remote-code-execution loader, not a normal icon fetcher. The absence of lifecycle hooks limits automatic activation but does not remove the concrete runtime attack...

This is a concrete remote-code-execution loader unrelated to the documented mutex functionality. Lack of lifecycle hooks does not mitigate execution when the exported API is called.

This is a concrete remote-code-execution loader, not a package-aligned API implementation. Lack of an install hook limits automatic activation but does not remove the malicious runtime be...

The postinstall hook concretely performs unconsented mutation of the consuming project's .claude control surface. Although its content is a benign guide and no exfiltration was found, thi...

Source inspection confirms the lifecycle hook mutates a third-party AI-agent package. Under the install-control-surface policy, this warrants blocking even though the patch is narrow and...

The lifecycle script silently hijacks another package's namespace, and runtime code performs undisclosed remote-controlled activity through user credentials. These are concrete malicious...

The package's calendar utilities do not justify an import-time hidden executable drop into the Windows Startup folder. This is concrete persistence behavior despite having no npm lifecycl...

Source inspection confirms concrete credential and customer-data transmission to a concealed hard-coded HTTP endpoint. This is malicious exfiltration behavior despite requiring a user-inv...

The package has no install hook, but its normal runtime path silently harvests host application/process metadata and transmits it through its default remote LLM request path. This is a co...

The Node import path contains an unconditional, unrelated detached-process launch and database connector invocation. This is concrete unauthorized runtime behavior, not an inert scanner s...

Source directly implements unconsented install-time host-data collection and external exfiltration. This is concrete malicious behavior, not a package-aligned feature.

The concealed remote control of unsolicited authenticated WhatsApp actions is concrete malicious runtime behavior. The lifecycle alias mutation adds further unrequested install-time modif...

The concealed, remote-controlled authenticated action is concrete malicious behavior at normal runtime. The missing postinstall script is separately broken but does not negate the runtime...

This is concrete remote-controlled, unconsented use of the caller's authenticated WhatsApp account, not a package-aligned newsletter API feature. No install hook is needed for the payload...

The remote, concealed, dynamically compiled payload is a concrete remote-code-execution mechanism, not ordinary database connectivity. Lack of an install hook limits automatic activation...

This combines unconsented install-time replacement of a foreign package identity with concealed runtime behavior controlled by a remote list. The behavior is not required by the documente...

Concrete install-time dependency replacement and concealed runtime network activity establish malicious behavior. The ordinary media helpers do not mitigate those independent attack paths.

The import-time, detached execution of an unrelated unconstrained dependency is a concrete hidden execution chain, not normal testing-plugin behavior. Absence of an explicit URL does not...

The advertised utility package contains an undocumented remote code loader whose payload is controlled by a hard-coded external endpoint. Although it is not install-time execution, this i...

This is a concrete staged remote-code-execution mechanism, not a benign CDN fetch. Lack of automatic invocation reduces reachability but does not remove the malicious capability exposed b...

The bundled rulesets contain a concrete credential/data forwarding chain in two target-browser artifacts. No install hook is needed for the payload to be harmful once a consumer loads the...