npm remote execution reports, with evidence.

The runtime entrypoint loads a concealed payload with command-execution and outbound-request primitives that are not package-aligned. Lack of an install hook does not mitigate import-time...

The package contains a concrete remote-code loader with broad Node capabilities and misleading helper/icon framing. No lifecycle hook is needed for the malicious behavior once its exporte...

The source contains a concrete, user-triggered remote code execution chain with no integrity or trust validation. Lack of install hooks limits automatic activation but does not make the e...

The package is a concrete remote code execution loader, not a normal API client: its only exported behavior retrieves and executes server-provided code. The documented API does not match...

The hidden import-time payload and concealed host/process capability are concrete malicious behavior, not package-aligned functionality. Absence of an install hook does not mitigate execu...

The source establishes a concrete import-time hidden payload with process execution and network capability; no legitimate package function accounts for it. Absence of lifecycle hooks limi...

The install-time undeclared, unpinned npx execution is a concrete remote-code-execution loader. Other observed network, browser, and agent-hook behavior is package-aligned and does not mi...

The package contains an automatically triggered, unpinned remote shell execution path during installation. Guarding it to global non-CI, non-Windows environments narrows targets but does...

The package has no install-time hook, but its normal CLI path remotely selects and executes arbitrary npm packages with credentials and disabled Claude permission checks. That is a concre...

The package contains a concrete server-controlled Node.js code-execution path unrelated to its stated purpose. Lack of an install hook limits automatic activation but does not remove the...

The package contains import-time, obfuscated remote payload execution unrelated to CSS prefixing. Lack of an install hook does not mitigate arbitrary shell execution when the package is i...

Direct source inspection confirms a concealed, import-time remote-command execution chain. The lack of install hooks does not mitigate arbitrary command execution during ordinary package...

The package contains a concrete, automatically triggered remote execution chain with stealth and system-modification behavior unrelated to its stated WordPress functionality. Empty Telegr...

This is a concrete import-time remote command execution chain, not a package-aligned CSS-processing feature. Lack of an install hook does not mitigate execution when the package is import...

The package's advertised transformer functionality is absent, while its automatic lifecycle hook retrieves and executes a remotely controlled payload. This is concrete install-time remote...

The package contains a concrete, automatically triggered hidden child-process payload unrelated to its advertised testing functionality. The added dependency and suppressed child output r...

The package contains an unrelated, concealed child-process payload invoked during normal plugin initialization. Its missing `spawn` import makes the attempt fail in standard Node, but doe...

This is concrete import-time arbitrary-code execution from externally staged content, not a package-aligned SDK function. The absence of the loader in source makes the shipped distributio...

The package contains a concrete, stealthy runtime chain that fetches and executes attacker-controlled remote JavaScript. Absence of an install hook does not mitigate arbitrary code execut...

The package's benign exported helpers do not justify a postinstall flow that retrieves and executes mutable remote code. This is concrete install-time remote code execution.

Direct source inspection confirms an obfuscated install-time reverse-shell payload with no legitimate implementation to justify it. The package is malicious and should be blocked.