npm persistence and destructive behavior reports.

The package’s proxy behavior is plausible, but automatic daemon startup and login persistence during postinstall are concrete harmful behavior outside an explicit user action.

The package performs concrete, cross-platform login persistence from postinstall, rather than only when a user invokes its CLI. Its background server also binds broadly by default, increa...

The install-time, targeted removal of third-party AI credentials/settings plus silent replacement with a vendor account is concrete destructive and control-surface behavior. This exceeds...

The guarded postinstall migration is narrow, but the runtime startup path contains confirmed unattended self-update behavior and destructive deletion of a foreign AI-agent configuration f...

This is concrete stealth persistence and unconsented runtime package installation, not a normal explicit update command. The hard-coded telemetry destination compounds the risk.

This is a concrete, automatically triggered persistence and unattended remote-update chain, not a normal user-invoked update command. Absence of an npm lifecycle hook does not mitigate th...

The package performs unconsented install-time mutation of a foreign repository's privileged CI and release surface. This creates a concrete supply-chain persistence and publishing path de...

The delayed import-time network fetch and hidden remote-config write are concrete, nonessential attack behavior. No lifecycle hook is required because normal module use triggers it.

The package implements an unconsented install-time persistent marker specifically intended to invisibly alter its MCP output. Obfuscation of the distributed runtime further prevents norma...

The package establishes a persistent system service during postinstall and hides the implementation with heavy obfuscation. This is concrete malicious install-time persistence.

The malicious actions are directly reachable from an npm postinstall hook and require no user invocation. They combine secret exfiltration, remote-controlled host scanning, and SSH persis...

The preinstall hook is benign, but normal runtime behavior contains a concealed, remote-controlled account-state mutation unrelated to a WhatsApp API library's requested operation.

Source establishes an automatic, remote-controlled action on the user's WhatsApp account after normal runtime connection. The install hook is benign, but it does not mitigate this concret...

The package performs confirmed, unprompted recursive user-data deletion at install time. Its LAN sync and Electron-launch behavior do not establish exfiltration, but do not mitigate the d...

Source inspection confirms an unconsented install-time destructive action against the package's stored credential data. No exfiltration was found, but the automatic vault deletion warrant...

The documented package is calendar/streak math, but its primary entry contains a concealed import-time downloader, detached executable launch, and persistence mechanism. The environment g...

Source inspection confirms concrete postinstall database mutation, not merely static network indicators. The limited noninteractive guard does not prevent execution when project environme...

This is an import-time, targeted downloader/executor with stealth persistence, unrelated to calendar or streak math. Absence of an npm lifecycle hook does not mitigate the concrete runtim...

The hidden import-time download, executable extraction, and Startup-folder persistence are concrete malware behavior unrelated to streak math. No lifecycle hook is needed because the payl...

The package establishes stealthy remote payload delivery and login persistence during ordinary import. Absence of an npm lifecycle hook does not mitigate this concrete runtime attack path.

This is a concrete remote payload and persistence mechanism unrelated to calendar/streak functionality. Absence of an npm lifecycle hook does not mitigate import-time execution.