npm remote execution reports, with evidence.

Direct source inspection confirms import-time reverse-shell behavior in the package main entrypoint. The lack of lifecycle scripts does not mitigate execution when the entrypoint is impor...

Source inspection confirms an import-time reverse shell to a hard-coded external endpoint. The benign node file and absence of lifecycle scripts do not mitigate the malicious package entr...

Direct source inspection confirms import-time reconnaissance, exfiltration, and a reverse shell; this is not explained by the declared n8n node functionality. No lifecycle hook is needed...

Source inspection confirms concrete import-time exfiltration and a reverse shell to a hard-coded external endpoint. The absence of install hooks does not mitigate the malicious main-entry...

Source directly establishes credential/environment exfiltration and remote arbitrary code execution on ordinary package import. The lack of an install hook does not mitigate this active r...

This is a concrete concealed import-time arbitrary-code execution chain, not a package-aligned SDK feature. The detached process and inherited environment materially increase impact.

Published Node entrypoints contain concrete import-time staged code execution that is absent from the source tree. This is malicious behavior, independent of the package's legitimate bloc...

Source inspection confirms a remote-controlled command-execution path, not merely obfuscation or a scanner heuristic. The absence of an install hook does not mitigate the runtime MCP back...

Direct source inspection confirms an unverified remote payload is installed and executed automatically during `postinstall`. The benign exported helpers do not mitigate this concrete inst...

Source inspection confirms concrete postinstall remote payload execution, not merely suspicious primitives. The shipped API and documentation are also inconsistent with the installer beha...

Direct source inspection confirms an unconsented postinstall remote-code execution chain. The package contains no local formatter setup implementation that would justify this behavior.

This is an active remote-control and payload-deployment channel over an automatic default connection, not merely package-aligned logging. Its server-directed agent workspace mutation and...

This is a concrete import-time remote code execution chain unrelated to assertion-library functionality. The absence of lifecycle hooks does not mitigate execution triggered by normal pac...

This is an unconsented install-time remote-code loader hidden inside a small local utility package. The bundled math code does not justify downloading, installing, and executing a mutable...

This is a concrete remote-code-execution loader, not a database-connector feature. Lack of an install hook reduces automatic exposure but does not remove the malicious capability.

The package contains a concrete runtime exfiltration-and-remote-execution chain unrelated to its stated middleware/logger behavior. Absence of install hooks does not mitigate execution wh...

Direct source inspection confirms a remotely controlled arbitrary-code execution path exposed by the package runtime API. The absent lifecycle hook limits install-time behavior but does n...

This is a concrete, concealed remote-code-execution path reached by normal package use, not merely a suspicious primitive. The absence of install hooks limits automatic installation-time...

Direct source inspection confirms a concealed payload appended to the public CLI entrypoint and executed on every CLI invocation. The absence of an install hook does not mitigate this con...

The package contains concrete import-time arbitrary code execution through decrypted external payloads and detached child processes. The discrepancy between source entry/build configurati...

The package provides no library behavior; its import-time browser payload covertly embeds an externally controlled destination. The domain-rotation publishing helper reinforces intentiona...