npm remote execution reports, with evidence.

The automatic remote executable/wheel chain is paired with deliberate concealment and post-install rewriting, establishing a concrete stealthy staged-payload behavior. Embedded hashes do...

This is a concrete remote-code-execution loader, inconsistent with the documented utility package. Lack of an install hook limits automatic activation but does not remove the malicious ru...

The advertised library code is benign, but its postinstall hook silently stages and executes server-controlled code. This is a concrete malicious supply-chain execution chain.

The source implements a direct remotely controlled code-execution path; the lack of an install hook only limits activation to runtime use.

Source inspection confirms a concealed remote-response-to-Function execution chain, not merely suspicious primitives. Absence of lifecycle hooks limits the trigger but does not remove the...

The main entrypoint performs unconditional remote payload retrieval and dynamic execution. This is a concrete remote-code-execution chain, not a benign network use.

Source inspection confirms an import-time detached payload launcher and an obfuscated remote dynamic-code loader. The absence of lifecycle hooks does not mitigate runtime compromise on im...

The runtime-reachable, obfuscated blockchain-resolved loader executes attacker-supplied code and spawns a detached process. The benign postinstall hook does not mitigate this independent...

The harmless postinstall chmod does not mitigate the runtime unverified executable-fetch path. This creates a concrete remote-code-execution surface rather than a merely suspicious primit...

The automatic native-payload install is explicitly designed to bypass host download-security controls, then persists the payload through OS integration. Digest checking does not mitigate...

Source inspection confirms a concrete remote command-and-control path that invokes local coding agents without approval or sandbox protections. Explicit daemon installation is separate, b...

This is a concrete remote-control channel with arbitrary-root file read/write and local agent prompt execution, activated by a persistent daemon. The lack of install hooks reduces exposur...

The package contains a concrete remote command-execution channel in shipped runtime code, reachable through a documented CLI command. Absence of lifecycle hooks does not mitigate the resu...

Automatic unauthenticated remote code execution in an npm lifecycle hook is a concrete install-time attack surface. Runtime agent tools are package-aligned, but do not mitigate the lifecy...

Source establishes an installer-independent, remote privileged operator with filesystem and process control. This is a concrete backdoor rather than a normal WhatsApp bot administration f...

The install-time reverse shell is concrete, automatic remote command execution unrelated to date formatting. The package is malicious even though its auxiliary collection file is not invo...

The manifest directly defines an unconsented install-time reverse shell to a fixed external IP. The unused bundled reconnaissance/exfiltration script corroborates the malicious purpose.

Source establishes an install-independent remote privileged identity plus reachable file-write and restart capabilities. This is concrete remote code execution behavior, not a scanner-onl...

This package creates a concrete install-time remote-code-execution path and automatically invokes an AI-tool onboarding operation. Optional checksum comparison does not bind the payload t...

Direct inspection confirms a foreign, unauthenticated-by-trusted-key remote binary source in the CLI execution path. Same-origin checksum validation does not mitigate malicious mirror-con...

The shipped runtime contains a concrete remote-command execution path, not merely a risky primitive. Its explicit-user trigger does not remove the arbitrary server-supplied shell execution.