npm credential and data exfiltration reports.

The package deliberately routes npm credentials and uploaded content through an opaque third-party endpoint. This is concrete credential and data exfiltration behavior despite requiring a...

The custom Worker receives both the npm bearer token and package payload during normal browser publishing, while an embedded credential increases immediate exposure. This is concrete cred...

The package implements a credential-harvesting proxy for npm publishing, with an embedded npm token as an additional severe indicator. User interaction is required, but the credential tra...

This is concrete credential and data exfiltration through a third-party endpoint during the advertised publishing flow. The absence of an install hook does not neutralize the user-trigger...

The third-party endpoint receives an npm bearer token and user-selected package contents under misleading registry-publishing status text. This is concrete credential and data exfiltratio...

The explicit click does not neutralize the embedded credential or the non-npm proxy receiving both the bearer token and upload data. This is concrete credential and data exfiltration beha...

The code intentionally routes npm credentials and upload data to an unrelated Worker in its normal browser path. This is concrete credential and data exfiltration, not a package-aligned d...

Source directly establishes transmission of an npm bearer token and selected file payload to a non-npm endpoint under the package author's control. The hardcoded npm-style token further s...

This is concrete, unconsented runtime data exfiltration from an AI coding agent to a package-controlled endpoint. No lifecycle hook is needed because the exposed CLI directly activates th...

The package contains a concrete, exposed phone-number exfiltration path to an unrelated host with an abusive custom header. Its benign version-check preinstall hook does not mitigate that...

The package contains a concrete default-enabled data-export path to hardcoded external webhooks. It is not limited to an explicit user logging command or a caller-selected endpoint.

The hard-coded fallback recipient, automatic enabling of migrated jobs, and later outbound delivery establish a concrete exfiltration path. The lack of an npm install hook does not remove...

The package contains a concrete runtime path that silently transmits credential-bearing mail-account configuration to an unrelated external host. This is data exfiltration, not necessary...

The package contains a concrete, runtime-triggered project-metadata exfiltration path to a hard-coded endpoint and an unpinned remote binary execution path. The lack of an npm lifecycle h...

The source establishes an end-to-end credential collection and upload path to a fixed remote host, unrelated to the advertised local CLI console. The absence of an npm install hook does n...

The package performs automatic install-time collection and transmission of an environment credential. This is concrete credential exfiltration behavior, regardless of the stated license-c...

The automatic lifecycle hook extracts an environment credential and transmits it remotely. Although framed as license validation, it is an unconsented install-time credential-exfiltration...

The package performs automatic install-time transmission of an environment credential to a remote endpoint. No additional payload activity was found, but the credential disclosure is conc...

The package performs an automatic install-time disclosure of an environment credential to the network, while its stated validation outcome is non-enforcing. This is concrete credential-ex...

The package performs automatic install-time transmission of an environment secret, while swallowing the validation errors that would make that transmission necessary for enforcement. The...

The package automatically exfiltrates an environment credential during preinstall. The absence of destructive behavior does not remove this concrete credential-disclosure risk.