npm detections from LPM Firewall.

Source inspection confirms an import-time remote-code execution chain with no user action or payload integrity verification. The unused-looking telemetry module contains the same download...

This is concrete import-time remote code execution, not telemetry: an opaque remote binary is downloaded, dropped, and launched detached. The lack of lifecycle hooks does not mitigate the...

The hidden loader is reachable on ordinary import and executes unauthenticated remote payloads. Its telemetry naming and opt-out variables do not constrain the downloaded binary's behavior.

This is a concrete import-time downloader-and-executor chain unrelated to the documented adapter API. Absence of lifecycle scripts does not mitigate arbitrary payload execution when consu...

This is a concrete import-time remote payload retrieval and execution chain unrelated to the advertised substring interface. The lack of lifecycle scripts does not mitigate the reachable...

This is a concrete remote payload execution chain reachable by ordinary import, not telemetry. The auxiliary telemetry source contains the same downloader/executor pattern but is not need...

This is concrete import-time remote payload execution unrelated to the declared semver API. Absence of an npm lifecycle hook does not mitigate the runtime RCE path.

This is concrete import-time remote payload execution with no integrity validation or user action beyond importing the package. Absence of an npm lifecycle hook does not mitigate the reac...

This is a concrete, automatic remote payload execution chain triggered by import, unrelated to the package's minimal exposed API. The large telemetry module contains the same capability p...

The package executes a remote, unauthenticated native payload during ordinary import and conceals failures/output. This is concrete malware behavior, not normal telemetry.

This is a concrete import-time remote code execution chain with no package-aligned purpose. The lack of lifecycle hooks does not mitigate execution on normal package use.

The package contains an import-time staged payload loader that remotely obtains and executes arbitrary native code without consent. This is concrete malicious behavior, not telemetry.

This is a concrete import-time remote-code-execution chain with no integrity validation or user action beyond loading the package. The unused telemetry module contains a substantially sim...

This is concrete import-time staged remote code execution unrelated to the documented mock-data functionality. The lack of an npm lifecycle hook does not mitigate execution when consumers...

This is a concrete import-time staged payload execution chain, not telemetry: the payload source is obfuscated, unverified, dropped to temp storage, and launched detached. The unused tele...

The behavior is concealed, unrelated to a code-style package, and remotely controlled at import time. Absence of npm lifecycle hooks does not mitigate this reachable execution chain.

This is a concrete import-time remote-payload execution chain unrelated to the stated UI package purpose. The absence of lifecycle hooks does not mitigate execution on ordinary package use.

Source inspection confirms the lifecycle hook silently performs broad cross-agent configuration and instruction injection. This meets the publish-block policy regardless of the absence of...

This is concrete, repeated exfiltration of local AI-agent conversations triggered by routine use, with no README disclosure or per-launch consent. It is not an install-hook case, but is m...

The lifecycle behavior meets the block boundary: postinstall automatically mutates persistent Claude Code and other AI-tool control/configuration surfaces. Opt-in harvest networking does...

The lifecycle hook directly performs broad foreign AI-agent registration and instruction-file mutation without an explicit user command. This meets the install-control-surface block crite...