npm remote execution reports, with evidence.

The source establishes an unconditional import-time remote-code-execution chain. It has no package-aligned functional safeguard or integrity validation.

The concealed remote payload loader is concrete arbitrary code execution, not required for the documented SVG functionality. Absence of install hooks limits automatic activation but does...

The automatic, concealed runtime installation and execution of an unrelated dependency is concrete malicious behavior, not required for a Rollup polyfill plugin. No lifecycle hook is need...

The package’s import-time launcher directly executes a bundled Windows binary whose embedded strings demonstrate C2, command execution, persistence, and update behavior. This is concrete...

This is not a benign native dependency: importing the package launches a bundled C2-capable PowerShell agent that persists on the host. The absence of an install hook does not mitigate th...

This is concrete import-time staged remote code execution, not a package-aligned feature. The absence of lifecycle hooks does not mitigate the reachable malicious entrypoint.

This is an import-time, concealed remote payload path unrelated to the advertised UUID API. Its current README-dependent guard does not neutralize the Windows remote-code-execution behavior.

Direct source inspection confirms an import-time remote payload fetch followed by eval with no validation. This is a concrete remote-code-execution chain, not merely a static hint.

Source inspection confirms an import-time remote-payload loader with dynamic execution. This is a concrete arbitrary-code-execution chain, not merely a static hint.

Concrete import-time remote payload execution and persistence behavior is present in the package's default entrypoint. The benign helper functions and store do not mitigate this attack ch...

This is a concrete, undisclosed import-time remote code execution chain unrelated to a UUID package. The absence of lifecycle hooks does not mitigate the automatic runtime trigger.

Source directly establishes an automatic import-time remote payload download and execution chain. This is concrete malicious behavior, independent of scanner labels.

The package contains concrete, unconditional remote-code execution at import time. Its inert-canary documentation is contradicted by the source.

Despite inert-canary comments, the source contains concrete import-time remote code execution. No install hook is needed for this to be malicious.

The package has no install hook, but its exported main file creates concrete remote code execution whenever it is imported. The source comment falsely describes the package as inert.

The concealed remote payload execution path is unrelated to the advertised SVG utility and creates concrete arbitrary code execution. Lack of lifecycle hooks limits automatic activation b...

The decoded, hidden install and immediate execution of an undeclared package are concrete malicious behavior, not polyfill functionality. Absence of a lifecycle hook does not mitigate imp...

The import-time hidden package installation and execution are concrete malicious behavior, not required for the declared polyfill functionality. The ESM entrypoint’s absence of this code...

The CJS entrypoint implements a concealed remote payload loader and executor unrelated to SVG processing. No lifecycle hook is needed for this concrete runtime RCE capability to be malici...

The entrypoint contains a concrete, obfuscated import-time chain that installs and executes an undeclared remote package. No lifecycle hook is needed for this behavior to affect consumers...

This is a concrete remote code-execution loader, not package-aligned icon functionality. Absence of an install hook does not mitigate the runtime execution path.