npm credential and data exfiltration reports.

The source implements concrete, automatic exfiltration of host identity and user design identifiers to an unrelated external analytics endpoint. The absence of an install hook reduces sco...

This is a concrete automatic install-time credential and data-exfiltration chain, not package-aligned setup. The benign runtime client does not mitigate the malicious lifecycle behavior.

This is a concrete automatic credential-exfiltration path, not functionality required by the SDK entrypoint. The postinstall trigger makes it run without a user command.

The source establishes a direct path from local third-party credential files to serialized remote state. This is concrete credential exfiltration beyond ordinary local CLI operation.

The default endpoint and Bearer authorization path establish concrete credential forwarding to a non-package-aligned host. This is sufficient for a publish block despite requiring an expl...

Source establishes credential collection and upload to a default endpoint inconsistent with the package's stated Happy identity. The explicit command trigger does not remove the misleadin...

This package combines concealed runtime logic with capture and hub-delivery primitives for sensitive LLM traffic. Although it has no install hook, the concrete data-exfiltration surface w...

Source directly establishes credential submission to a fixed unexpected endpoint and persistence of its session routing. The lack of an install hook does not remove the credential-exfiltr...

The hidden cross-agent identity logic accesses a foreign private key and uses it to authenticate outbound requests for a pinned target. Opt-in telemetry does not mitigate this concrete ru...

The package contains a concrete remote credential and shell-input collection path, and the relevant exam command is deliberately obfuscated. The lack of an install hook does not remove th...

The extension implements a concrete path from credentials entered on arbitrary websites to an embedded remote server. The absence of an npm install hook does not neutralize this credentia...

The published runtime artifacts contain default real webhook destinations and a direct path from operation inputs to HTTP POST bodies. The lack of an install hook does not mitigate this r...

The package contains an active, default remote logging path to hard-coded third-party webhooks that transmits unconstrained application payloads. The lack of an install hook does not remo...

The package directly harvests a local GitHub token and transmits it to a non-GitHub endpoint. The absence of an install hook limits activation to CLI use but does not remove the credentia...

This package has no npm lifecycle hook, but its explicit global setup persistently modifies broad AI-agent control surfaces, uploads conversation content, and remotely updates the execute...

Source establishes an explicit-command persistence chain from broad AI-agent hooks to authenticated uploads at a hard-coded HTTP IP endpoint. The lack of an install lifecycle hook reduces...

This is concrete screenshot data exfiltration to a built-in third-party endpoint, not merely a local screenshot-review tool. The absence of an install hook reduces propagation risk but do...

This is concrete install-hook abuse and credential exfiltration, not merely a user-invoked account-management tool: the global lifecycle hook changes broad AI CLI control surfaces and the...

The fixed private endpoint, default credential, automatic tracing initialization, and POST export behavior establish a concrete runtime data-exfiltration mechanism. The absence of an inst...

The executable's fixed remote default and credential POST conflict with the documented localhost default. This is concrete credential-exfiltration behavior, even though it is triggered by...

Source establishes a credential-exfiltration path from a supported API-key CLI option to default third-party telemetry. No install lifecycle hook is present, but that does not remove the...