npm security reports, with evidence.

The package has no apparent package-aligned reason to collect and transmit this system data during installation. The exfiltration is concrete and automatically triggered.

Source confirms an import-triggered remote payload loader and detached execution chain. The absence of an npm lifecycle hook does not mitigate runtime compromise of package consumers.

This is a concrete import-time remote-code-execution chain unrelated to the advertised state-store functionality. The opt-out variables and telemetry README claim do not justify downloadi...

This is a concrete import-time staged-payload execution chain, not ordinary telemetry. The absence of lifecycle hooks does not mitigate execution when consumers import the package.

Direct source inspection confirms import-time download-and-execute behavior. The absence of an npm lifecycle hook does not mitigate execution on ordinary package use.

The documented telemetry claim is inconsistent with the import-time download-and-execute behavior. No lifecycle hook is needed because ordinary package import activates the payload chain.

This is a concrete remote-payload execution chain activated by importing the package, unrelated to the stated React-component purpose. No lifecycle hook is needed for the package to execu...

This is an import-time staged remote-code-execution chain unrelated to the advertised adapter or stated telemetry. No signature, hash, or user action protects the downloaded executable.

This is a concrete import-time remote-code-execution chain, not legitimate telemetry. Its obfuscated endpoints, DNS fallback, detached execution, and cleanup indicate malicious intent.

This is an import-time remote payload loader, not ESLint configuration behavior. Its stealthy download, temporary staging, and detached execution constitute concrete malicious RCE.

This is a concrete staged remote-code-execution chain hidden as telemetry, activated automatically during installation and import. The package has no legitimate drawer implementation that...

The advertised state-store package has an undeclared, import-triggered remote native payload loader and executor. This is concrete malware behavior, not ordinary telemetry.

Source inspection confirms import-time remote payload retrieval and detached execution, not ordinary telemetry. The package should be blocked.

The package implements covert import-time remote payload staging and execution, not ordinary telemetry. The no-lifecycle manifest does not mitigate this runtime RCE path.

The package implements an unconsented import-time remote payload loader and launcher, not normal telemetry. No lifecycle hook is needed because the behavior activates whenever consumers i...

This is concrete, automatic remote code execution hidden behind purported telemetry in a React component package. The absence of an npm lifecycle hook does not mitigate import-time execut...

This is a concrete import-time remote code execution chain unrelated to the advertised ESLint/config package purpose. The absent npm lifecycle hook does not mitigate automatic execution o...

This is an import-time remote payload loader and executor, not ordinary telemetry. The opt-out and lack of npm lifecycle hooks do not mitigate the unconsented runtime execution chain.

The package has no install hook, but ordinary import causes a hidden downloader/dropper to execute an unauthenticated remote native payload. Its behavior is incompatible with the stated R...

Source confirms an unconsented postinstall mutation of a foreign AI-agent control surface via externally fetched code. This meets the install-control-surface blocking boundary.

This UI package contains a concrete remote-payload execution chain unrelated to its stated functionality. The postinstall hook suppresses errors, increasing stealth.

The package contains a default-enabled, hardcoded external receiver for application records rather than merely offering caller-configured telemetry. This establishes concrete unconsented...

The install hook concretely mutates foreign AI-agent control surfaces without consent and executes an integrity-unverified remote binary. The global-install guard and opt-outs do not remo...

Source inspection confirms an unconsented postinstall mutation of broad, foreign AI-agent control surfaces. This meets the blocking policy regardless of the loopback endpoint.

This is concrete, automatic abuse of a connected third-party account rather than a package-aligned API exposed for caller use. The benign preinstall hook does not mitigate the runtime pay...