npm remote execution reports, with evidence.

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...

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...

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...

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...

This is a concrete staged remote-code-execution chain hidden behind a transaction-data API. The absence of lifecycle hooks does not mitigate runtime execution after an ordinary library call.

This is a concrete remote-code-execution loader, not a benign dynamic evaluation pattern. It is runtime-triggered rather than install-time, but warrants blocking because an untrusted remo...

The package performs concealed import-time remote payload execution unrelated to its declared text-helper functionality. This is concrete malware behavior.

The package implements an immediate remote-payload loader and dynamic evaluator with no integrity check, user action, or package-aligned functionality. This is concrete remote code execut...

This is a concrete remote-code-execution loader disguised as a Tailwind plugin. Absence of an install hook limits the trigger but does not mitigate execution when the exported plugin is u...

The payload executes on package import and has a concrete network-to-eval-to-detached-process chain. The absence of lifecycle hooks does not mitigate import-time arbitrary code execution.

Direct source inspection confirms an unconsented install-time reverse shell with a hard-coded command-and-control endpoint. The benign date formatter does not justify this behavior.

The package deliberately hides an auto-running browser loader that remotely retrieves and evaluates code. Its lack of an install hook reduces install-time scope but does not remove the co...

The source implements an obfuscated remote-code loader with automatic browser activation. Absence of lifecycle hooks limits install-time impact but does not remove the concrete runtime RC...

The appended import-time payload is unrelated to a Tailwind forms plugin and contains concrete obfuscated staging, eval, and detached process execution. The lack of lifecycle hooks does n...

This is concrete malicious runtime behavior unrelated to mutex functionality, including host reporting and remote code execution. Absence of lifecycle hooks does not mitigate the callable...

This is a concrete install-triggered C2 and remote-control chain, not merely a bundled desktop application. The lifecycle hook runs it without an explicit user command.

This is a concrete staged remote-code-execution path, not a benign CDN fetch: server-controlled content is dynamically executed with privileged Node globals. Absence of lifecycle hooks li...

The source implements a concrete staged remote-code-execution path, despite requiring an explicit exported-function call. Its declared utility purpose and documentation do not justify thi...

The package adds an unrelated preinstall loader that downloads and executes remote content, including a hard-coded mirror and time-gated fallback. This is concrete install-time remote cod...

The runtime entrypoint contains an explicit remote download-and-execute chain, corroborated by a bundled file that invokes it. Absence of an install hook does not mitigate this concrete r...