npm credential and data exfiltration reports.

Direct source inspection confirms automatic credential upload to a fixed external receiver. The lack of npm lifecycle hooks does not mitigate this runtime exfiltration path.

The package contains a concrete automatic credential-upload path to a fixed third-party endpoint. Lack of an npm lifecycle hook limits activation but does not remove the runtime exfiltrat...

The source establishes a concrete default runtime path from business-operation records to embedded external webhooks. The absence of install hooks does not mitigate this runtime data-exfi...

Direct inspection confirms a concrete automatic reconnaissance-and-exfiltration chain, not merely suspicious primitives. The benign UI entrypoint does not justify the install-time behavior.

This package silently substitutes a package-controlled remote API for direct Facebook credential login and sends supplied credentials there by default. No install hook is needed for this...

Normal email-client networking does not justify silently exporting account configuration to an unrelated logging endpoint. The harmless scoped postinstall hook does not mitigate this runt...

Runtime source directly sends serialized IMAP configuration, including a possible password field, to an external logging host. The benign workspace-symlink postinstall does not mitigate t...

This is concrete runtime data exfiltration through automatic clipboard collection and remote POSTs, supplemented by screenshot upload capability. The absence of lifecycle hooks does not r...

The source establishes a concrete, automatic credential-transfer chain to a fixed external receiver. Documentation frames this as vault migration, but it does not remove the unconsented e...

The package contains a concrete automatic secret-upload path to a fixed remote host. The absence of install hooks reduces scope but does not negate the runtime credential exfiltration beh...

Source confirms a default-enabled runtime path that transmits API credentials and arbitrary upstream environment values to an external endpoint. The interaction requirement reduces breadt...

This is concrete, obfuscated, install-time data exfiltration with no user action beyond installation. It meets the blocking threshold.

This is concrete credential exfiltration during package runtime, despite no npm lifecycle hook. The explicit workflow template materially enables the transfer.

This is a concrete install-time data-exfiltration chain with obfuscation and shell execution. It is malicious, not package-aligned behavior.

This is not limited to user-invoked local setup: a connected remote RPC surface can export and replace third-party AI-agent credentials. The benign postinstall helpers do not mitigate the...

Source establishes a default, recurring export of Claude-derived activity data to a hard-coded external IP. The absence of an npm lifecycle hook does not mitigate the concrete exfiltratio...

The package contains a concrete credential-exfiltration path: automatic import of Happy credentials followed by authenticated transmission to an unrelated hard-coded host. The absence of...

Source establishes a default external receiver and automatic periodic POST of locally collected work data. The absence of an npm lifecycle hook does not remove the concrete exfiltration b...

This is concrete, unconsented install-time collection and external exfiltration of sensitive host data. The package contains no legitimate implementation that would justify this behavior.

The package has a concrete remote upload path for broadly collected credentials and project data. Explicit command activation and documentation reduce stealth but do not mitigate the unsa...

This is concrete, default-enabled data exfiltration to a hardcoded third-party endpoint after installation. It is not justified by an npm lifecycle hook, but user invocation does not cure...