Malicious packages, on record.

This is concrete credential exfiltration to a fixed third-party endpoint, not required for normal Facebook session emulation. The copied example additionally opts into installing a foreig...

This is concrete credential and telemetry exfiltration to a fixed unofficial plaintext endpoint, despite requiring user-invoked setup. No lifecycle hook is needed for the harmful chain on...

Source establishes automatic upload of real environment-derived secrets to a fixed external receiver during normal CLI execution in GitHub Actions. This is concrete credential exfiltratio...

Direct source inspection confirms a hardcoded, enabled-by-default external telemetry upload of rich local AI/work-project data. The absence of an npm install hook does not remove the conc...

Source confirms default telemetry of rich runtime context and unprompted global updates on every CLI invocation. The harmless postinstall locator does not mitigate these runtime behaviors.

The package contains a concrete default-on data-exfiltration path to hardcoded third-party Telegram recipients during ordinary user scans. No lifecycle hook is needed for this runtime beh...

The package contains an active, hard-coded third-party Telegram reporting channel that automatically exports user scan activity and results. Absence of lifecycle hooks does not mitigate t...

The source implements automatic third-party reporting to package-controlled Telegram recipients during normal scanner use. That unconsented disclosure is a concrete data-exfiltration beha...

The package contains a concrete, default-enabled reporting path to package-controlled Telegram recipients during normal use, with an additional QR relay capability. This is unconsented da...

The normal user-invoked scanner exfiltrates operational results to package-controlled Telegram recipients by default. No install-time hook exists, but the concrete automatic reporting cha...

This is a concrete, unconsented install-time credential-harvesting and internal-reconnaissance chain, not package-aligned runtime health behavior.

The install hook performs broad, unconsented environment harvesting and writes potentially secret data outside its package directory. Lack of observed network egress does not make the cre...

Source establishes a persistent fixed-endpoint credential setup followed by token-bearing network requests. No lifecycle hook mitigates install-time risk, but it does not remove the crede...

Source confirms concrete transmission of user command content and an authentication-like token to a remote endpoint. Although there is no install-time hook and the behavior is exam-trigge...

Direct source inspection confirms automatic credential upload to a fixed external receiver. The lack of npm lifecycle hooks does not mitigate this runtime exfiltration path.

The package contains a concrete automatic credential-upload path to a fixed third-party endpoint. Lack of an npm lifecycle hook limits activation but does not remove the runtime exfiltrat...

The source establishes a concrete default runtime path from business-operation records to embedded external webhooks. The absence of install hooks does not mitigate this runtime data-exfi...

Direct inspection confirms a concrete automatic reconnaissance-and-exfiltration chain, not merely suspicious primitives. The benign UI entrypoint does not justify the install-time behavior.

This package silently substitutes a package-controlled remote API for direct Facebook credential login and sends supplied credentials there by default. No install hook is needed for this...

Normal email-client networking does not justify silently exporting account configuration to an unrelated logging endpoint. The harmless scoped postinstall hook does not mitigate this runt...