npm credential and data exfiltration reports.

The package deliberately seeds an unauthenticated workspace with a fixed private HTTP OAuth authority and automatically uses it later. Although it is not install-time behavior, this is a...

Source inspection confirms credential forwarding to a fixed third-party endpoint on a reachable runtime path. The absence of install hooks does not remove the credential-exfiltration risk.

The package combines default LLM body collection, Hub-decryptable outbound trace envelopes, and pervasive deliberate obfuscation. Although it has no install hook, the runtime data-exfiltr...

Source confirms default remote execution and transmission of the user's Zavudev API key to a separate hard-coded endpoint. There is no lifecycle hook, but the credential transfer is a con...

The source establishes an automatic, hard-coded outbound upload path for potentially sensitive tool activity. Lack of an install hook limits the trigger to CLI use but does not remove the...

The package exports a cloud credential to a package-controlled endpoint. Although this is an explicit command rather than an install hook, the credential exfiltration is concrete and high...

The package automatically transfers environment-derived secrets to a fixed external default endpoint during GitHub Actions execution. The absence of an install hook reduces installation r...

Source inspection confirms a bundled all-sites credential collector that uploads accepted login secrets to a remote default endpoint. This behavior is materially unrelated to the advertis...

Direct source inspection confirms automatic install-time system mutation and runtime disclosure of WhatsApp content to a hard-coded external Telegram recipient. These behaviors establish...

This is a concrete credential-collection and transmission chain to a hard-coded raw-IP endpoint with TLS verification disabled. The lack of an npm lifecycle hook limits installation risk...

The package contains a concrete, default-enabled runtime data-exfiltration path to embedded external webhook receivers. There is no install hook, but that does not remove the runtime disc...

The package embeds active third-party webhook destinations and automatically sends serialized runtime records to them during normal module use. Although this is not install-time behavior,...

The package contains an automatic lifecycle hook that reads and transmits a credential from the consumer environment. Although framed as license validation, this is a concrete install-tim...

The package has a concrete automatic credential-transmission path in preinstall. The limited request payload does not remove the risk of exporting an environment secret during dependency...

The package has a concrete automatic install-time credential transmission path. Static icon exports do not justify sending an environment secret during installation.

The package deliberately forwards NPM bearer credentials and selected package data to an unrelated Worker during its advertised publishing flow. Although user-invoked and without install...

The opaque third-party proxy receives an npm credential and uploaded files, creating a concrete credential and data exfiltration path. The absence of install hooks does not remove this us...

The source implements concrete credential and package-data transmission to an unrelated endpoint. User interaction is required, but it does not make forwarding an npm bearer token and arc...

This is a concrete credential and data-exfiltration path through an undisclosed third-party proxy. It is user-triggered rather than install-time, but the token-routing behavior warrants b...

This is a concrete credential-exfiltration path disguised as an npm publisher, reinforced by an embedded NPM credential. The lack of lifecycle hooks does not mitigate the malicious behavi...

This is concrete credential and source-data exfiltration through an opaque third-party relay. User interaction does not make forwarding an npm bearer token to that host safe.