npm credential and data exfiltration reports.

Source establishes a default-enabled recovery path that forwards sensitive Facebook credentials and an optional 2FA secret to an unrelated hardcoded host. This is concrete credential exfi...

Source establishes a concrete, default-enabled credential-exfiltration path to a third-party endpoint during normal login. The lack of lifecycle hooks does not mitigate this runtime accou...

Source directly shows credential submission to a hardcoded non-platform endpoint and an enabled-by-default automatic trigger. This is concrete credential exfiltration, notwithstanding the...

Source confirms a default third-party credential relay in the primary login path. Absence of lifecycle hooks does not mitigate the concrete credential-exfiltration behavior.

The package’s primary login path sends credentials to an unrelated hard-coded endpoint rather than Facebook. This is concrete runtime credential exfiltration, not merely a suspicious prim...

The package implements concrete background persistence and collection/upload of AI transcript-derived data on ordinary CLI execution. The lack of an npm install hook reduces propagation r...

The package contains a concrete credential-exfiltration path: sensitive runtime tokens are passed to a hardcoded external telemetry receiver. Absence of lifecycle hooks limits the trigger...

Source establishes a default third-party receiver and a direct credential/2FA POST reachable from the normal login path. The absence of install hooks does not mitigate this runtime creden...

Source directly confirms credential exfiltration to a package-configured third-party endpoint during the normal login path. No install hook is needed for this concrete runtime attack.

The package implements a default-enabled flow that forwards Facebook credentials to an unrelated hard-coded external host, establishing concrete credential exfiltration at normal runtime....

The shipped runtime contains default, non-placeholder external logging endpoints and automatically sends rich application records after initialization. This is a concrete default data-exf...

Source directly implements remote transmission of sensitive interactive-command and identity data, not merely package-aligned challenge submission. The absence of an install hook does not...

Source directly implements and documents transmission of user Facebook credentials to a non-Facebook hard-coded service during automatic recovery. The lack of an install hook does not rem...

Source directly establishes a default external credential submission path during automatic recovery. Documentation does not remove the security impact of sending passwords and 2FA secrets...

A package-selected external service receives raw Facebook credentials during normal recovery behavior. This is concrete credential exfiltration, despite requiring a runtime login/session-...

Source inspection confirms concrete credential exfiltration to a hard-coded non-Facebook endpoint during normal runtime login. No lifecycle hook is needed for this credential-theft behavior.

Source confirms a default third-party endpoint receives supplied Facebook credentials and optional 2FA data during the normal credential-login path. This is concrete credential exfiltrati...

The source establishes a reachable, hard-coded third-party recipient for WhatsApp message data. The token gate does not remove the unauthorized disclosure behavior.

This is a concrete credential-harvesting and data-exfiltration chain, not merely a browser automation capability. Lack of install hooks does not mitigate the runtime behavior.

The main runtime bundle contains a hard-coded authenticated external data store that receives configured KB content. Although it is not install-time behavior and requires vector-KB enable...

The package contains a concrete, Hub-triggered export of an E2EE master key that conflicts with its security claims. This is not install-time behavior, but it is a confirmed credential/pr...