npm remote execution reports, with evidence.

Shipped code hides from agent sessions, tampers with OS security controls, executes a remotely supplied command, and writes foreign AI-assistant MCP configs to the current executable. The...

The package contains an active remote-script execution path driven by a service request, not merely a configurable API client or inert payload. The lack of an install hook does not remove...

The published node is fully obfuscated and, on import, runs a concealed Go WebAssembly payload after exposing Node filesystem and OS APIs to it. That is hidden code execution in the host...

The package combines security-control weakening with unauthenticated remote command execution. This is concrete malware behavior, not a benign installer capability.

The MCP handler sends environment values to the fixed portal and executes a command taken from that response, while the launcher can background-install a newer global release. That is rem...

The default portal is operator-controlled, and the MCP install tool executes that portal's install_command while forwarding env_vars. That is remote command execution reached through the...

The postinstall hook fetches native binaries from a CDN and makes them executable, using a checksum served by the same host, including static.jingyunyilian.com. The published server then...

The plugin silently detaches a native stage0 binary whose embedded profile inventories the home directory, forwards the process environment, and contacts unrelated skyleen.fr control serv...

Load-time execution in the main and CLI bundles extracts a concealed command from a bundled JPEG and runs it through hidden PowerShell, which is a concrete remote-code dropper. The readab...

The package has no install hook, but its active browser entrypoint automatically executes a remotely hosted, mutable JavaScript payload. This is concrete remote code execution exposure ra...

A shortened, redirected remote payload piped to Bash is a concrete remote-code-execution sink. Its placement in a work-time command makes the behavior deceptive and malicious.

The active remote control path evaluates received JavaScript and exposes unrestricted host RPC. This is concrete remote code execution, not merely a configurable client capability.

The package ships a hardcoded curl-to-shell remote execution path and a caller that invokes it, including a CI job that updates from a local registry first. There is no install lifecycle...

The package creates an automatic install-time path from an unverified remote archive to installed native code. Obfuscation and the absence of integrity validation make this concrete remot...

This is an automatic lifecycle remote-payload chain with no integrity verification and disabled TLS validation. It creates a concrete route for arbitrary code execution through a remotely...

This is concrete import-time environment exfiltration followed by remotely supplied code execution. The lack of an install hook does not reduce the risk to consumers that load the package.

This is concrete concealed code execution, not environment configuration behavior. The automatic entrypoint calls and hidden encoded PowerShell launcher warrant blocking publication.

The automatic lifecycle hook downloads and installs remotely controlled executables, then runtime code executes one of them. This is a concrete remote-code-execution supply-chain path, no...

The fetch-to-new-Function chain is concrete and reachable through an unvalidated message event. Although there is no install hook, the runtime behavior warrants blocking.

The package contains a reachable automatic remote-code execution path: curl output from a package-controlled endpoint is piped to sh. The lack of an npm install hook does not mitigate exe...

The remote-origin allowlist, token disclosure, and shell sink form a complete command-execution chain. The absence of an install hook does not remove the runtime backdoor.