npm remote execution reports, with evidence.

The automatic lifecycle hook creates a concrete unconsented remote-code-execution chain. Its apparent runtime-bootstrap purpose does not mitigate executing mutable network content during...

The package contains a concrete remote code execution chain hidden behind its public API. The lack of lifecycle hooks limits automatic installation execution but does not mitigate the mal...

The package contains a concrete remote-code-execution chain activated by normal runtime use. Lack of an npm lifecycle hook limits installation impact but does not mitigate the malicious r...

Source directly implements a remote download-and-execute chain through Bash. Although it is not install-time, it is an exported package capability with a concrete malicious payload endpoint.

This is an unconsented postinstall remote-code loader disguised as an install check. The packaged library itself is benign math, but its lifecycle hook creates a concrete execution chain.

This is a remote-code bootstrap executed automatically at install time, with trust rooted solely in a remotely served manifest. It creates a concrete install-time arbitrary-code-execution...

This is a concrete runtime remote-code-execution loader embedded in an ostensibly SVG package. Lack of install hooks does not mitigate the browser execution path.

The package performs concrete unconsented postinstall remote payload download and execution, not merely user-invoked setup. This warrants blocking regardless of whether the named endpoint...

The package performs unconsented postinstall remote payload execution, not merely first-party configuration. This is a concrete install-time RCE supply-chain risk.

Source inspection confirms a package script retrieves and executes an unauditable remote payload. The normal MCP server code does not justify that behavior.

This is a concrete remote-code-execution chain, activated during normal dotenv configuration and concealed by an obfuscated endpoint. It is not install-time, but it is malicious runtime b...

The package has no install-time hook, but its normal cloud-join path executes unvalidated remote commands and a downloaded shell script, then uploads captured interactive terminal data. T...

The package has no install hook, but its delivered SVG directly executes an unrelated remote script and installs a request-intercepting proxy service worker at browser runtime. This is co...

The package contains a concrete server-directed remote-code execution path and substantial browser-context collection. Its lifecycle hook is not install-time, but that does not mitigate t...

The source contains an unconditional import-time remote-code loader. This is concrete malicious behavior, irrespective of the lack of lifecycle hooks.

This is concrete, unconsented install-time remote code execution, not merely a user-invoked downloader. Platform and global-install guards reduce reach but do not remove the attack surface.

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

This is a concrete install-time remote payload chain designed to evade platform download-security controls, not a benign library dependency. The bundled checksum does not mitigate the pac...

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