npm credential and data exfiltration reports.

Direct source inspection confirms a concealed redirect chain, not merely a static scanner signal. Although it has no install hook, its browser payload is concretely deceptive and forwards...

The only declared entrypoint is a deceptive, obfuscated redirector rather than a legitimate npm library. Its runtime behavior establishes a concrete phishing/data-transfer attack surface.

Source confirms persistent agent-hook installation and default outbound collection to a hard-coded non-domain endpoint. The lack of an npm lifecycle hook reduces install-time risk but doe...

The package’s stated telemetry purpose does not justify default persistent hooks that harvest multiple AI-agent session stores and transmit their metadata to a hard-coded, non-TLS IP endp...

Concrete source establishes automatic credential-bearing configuration exfiltration to an unrelated endpoint. This is malicious despite otherwise package-aligned email and OAuth networking.

Source directly shows unconsented remote transmission of account configuration, including a path that serializes credentials. This is concrete credential exfiltration, not package-aligned...

This is a concrete runtime data-exfiltration path, not merely package-aligned IMAP/OAuth networking. The benign install hook and localhost MCP interface do not mitigate it.

Source directly establishes unconsented runtime credential-capable exfiltration. The install hook itself is benign, but it does not mitigate the Android data-exfiltration path.

The package contains an active runtime path that serializes sensitive IMAP configuration and silently sends it to an unrelated remote logging endpoint. The benign postinstall hook does no...

Source establishes automatic transmission of sensitive account configuration to an unrelated endpoint. The install hook itself is benign, but it does not mitigate the concrete runtime exf...

Source establishes an automatic external transmission of user mail-account metadata, not merely package-aligned mail-provider traffic. The benign lifecycle hook and loopback MCP server do...

This is a concrete credential-exfiltration path, not merely package-aligned mail or Google Drive traffic. No install hook is required, but ordinary Android runtime initialization activate...

Concrete runtime credential/configuration exfiltration to an unrelated endpoint is present in shipped JavaScript. No install hook is required for this malicious behavior.

Source establishes an unconditional, non-package-aligned network disclosure of account data and potentially credentials during ordinary runtime. The benign workspace postinstall hook does...

The source establishes an unconsented remote logging path that can carry IMAP credentials, not merely package-aligned mail-provider traffic. The benign install hook and local token-gated...

The package contains a default-enabled path that transfers environment secret values to a package-controlled external endpoint during normal GitHub Actions execution. No install hook is r...

The package has no install-time attack, but its obfuscated runtime silently exfiltrates substantial user source content on ordinary tool failures. That is a concrete privacy and data-exfi...

Source establishes a concrete, default-enabled remote transmission of environment secrets during CI execution. The lack of an install hook does not mitigate this runtime credential-exfilt...

The hard-coded receiver and enabled-by-default periodic export establish concrete unconsented data exfiltration. The lack of an npm install hook does not negate runtime behavior after the...

Source confirms an automatic telemetry path backed by a hard-coded secret, not merely a scanner pattern. The scoped postinstall symlink is not the malicious behavior.

This is concrete default-on data exfiltration of user and repository identity, amplified by cross-agent configuration discovery. Explicit cloud features and guarded CI setup do not mitiga...