npm credential and data exfiltration reports.

Source establishes credential exfiltration to a remote hub configured through the package's command surface. No install hook is involved, but the undisclosed backup behavior is concrete a...

This is concrete install-time screen-data exfiltration via a bundled executable and JAR.

Source inspection confirms an install-time path to a hard-coded authenticated remote database plus privileged account and authorization-state mutation. This is concrete unsafe behavior fo...

The package performs automatic, persistent collection and remote transmission of user command content and host AI-tool inventory during ordinary use. This is a concrete unconsented data-e...

This is concrete, covert data-exfiltration behavior embedded in a package whose declared npm entrypoint is absent. Lack of an install hook reduces install-time exposure but does not make...

Although there is no install-time hook, the source contains a concrete, enabled GitHub Actions path that transmits environment secrets to a package-controlled default endpoint. Remote def...

Source directly implements transmission of environment-derived credentials to a hardcoded third-party endpoint. The absence of an install hook reduces reachability but does not remove the...

The source establishes a concrete, automatic credential-upload path to a package-vendor endpoint controlled by remotely hydrated definitions. The absence of an npm install hook reduces ex...

The package implements concrete, undisclosed runtime exfiltration of user-entered notebook content to a remote audit endpoint. This is stronger evidence than the noisy reverse-shell hint...

Source inspection confirms an automatic environment-secret upload to a hardcoded third-party endpoint, not merely network or shell primitives. No install hook exists, but the concrete CI...

Source establishes a concrete, reachable data-exfiltration path to a fixed third-party Telegram recipient. The token guard limits activation but does not make the hardcoded recipient cons...

Source establishes a concrete hardcoded operator backdoor plus remote storage of WhatsApp authentication state and message-data forwarding. The Termux preinstall mutation adds further unc...

Source inspection confirms a default third-party endpoint receives credentials on the normal login and auto-login paths. Documentation acknowledges an external API but does not remove the...

The package-default remote database receives WhatsApp authentication state, and fixed-recipient telemetry exposes paired-account metadata. These behaviors are reachable during normal runt...

Although npm installation has no install-time hook, the shipped extension combines broad all-site credential capture with a hard-coded remote default backend. That behavior is a concrete...

The source directly implements credential theft, remote command execution, C2 communication, and wallet draining; missing declared dependencies may impair execution but do not change its...

Direct source inspection confirms an install-triggered external exfiltration callback. The benign placeholder runtime export does not mitigate the postinstall behavior.

This is concrete credential exfiltration to a non-Facebook package-controlled default endpoint, not merely Messenger API traffic. No install hook is needed because the harmful path is rea...

The hardcoded remote database is active by default and receives WhatsApp credential material during normal runtime. This is concrete credential exfiltration, not merely a noisy scanner ma...

This is concrete credential exfiltration through a publisher-controlled default database reached during normal runtime. The Termux-only preinstall hook is not the decisive behavior.

This is a concrete credential-exfiltration and remote-control chain, not merely a WhatsApp bot feature. The benign Termux preinstall hook does not mitigate the runtime backdoor behavior.