npm credential and data exfiltration reports.

Source establishes a concrete remote-controlled browsing proxy with request and cookie handling, plus automatic third-party script execution. Although it lacks install hooks, this is mali...

Direct source inspection confirms an install-time lifecycle hook that performs host fingerprinting and external exfiltration. This is concrete malicious behavior, not merely a suspicious...

Static source inspection confirms runtime remote-code loading and a service-worker proxy that relays browser traffic and handles proxied cookies. Although there is no install-time Node ex...

No install-time behavior was found, but the shipped browser entrypoint loads a remote third-party script and configures an opaque proxied browsing stack that can handle request data. Thes...

This is not an ordinary npm library: its only entrypoint is an HTML app that loads unpinned remote code and installs a service worker to proxy traffic to unrelated remote infrastructure....

Direct inspection confirms an unconsented `postinstall` credential-exfiltration chain. The package contains no source functionality that would justify collecting and transmitting CI secrets.

Direct inspection of the sole package file confirms an automatic install-time AWS credential-exfiltration chain. This is concrete malicious behavior, not a scanner-only inference.

This is concrete, unconsented install-time host fingerprinting and external exfiltration with no apparent package functionality. The behavior warrants blocking publication.

Direct source inspection confirms import-time exfiltration in both package entrypoints to a non-package-aligned domain, including full environment variables. This is concrete malicious be...

Direct source inspection confirms install-triggered execution and concrete credential/file exfiltration. This is malicious behavior with no benign package purpose.

Source inspection confirms covert install/build-time execution via binding.gyp and external host fingerprint exfiltration. This is concrete malicious behavior, not package-aligned functio...

Direct source inspection confirms build-time execution and external exfiltration of local host identity data. The proof string explicitly indicates an ignore-scripts bypass, so this shoul...

Direct source inspection confirms install/build-time execution through binding.gyp and concrete host/CI metadata exfiltration to an external ngrok endpoint. The workspace file write and p...

Source inspection confirms concrete install-time execution that sends telemetry to a hardcoded Sentry DSN and queries public IP endpoints before the user imports the package. This is not...

Source inspection confirms concrete exfiltration to an external ngrok endpoint and unconsented workspace mutation, reachable through binding.gyp build evaluation and runtime entrypoint ex...

Source inspection confirms concrete install-time collection and exfiltration of host identity data to an external endpoint. This is malicious behavior, not merely suspicious network capab...

Source inspection confirms unconsented install-time secret harvesting and external exfiltration in postinstall.js. This is concrete malicious behavior, not package-aligned SDK functionality.

The provided scanner snippets indicate concrete install-time exfiltration behavior, but finalization requires direct source inspection and this environment did not permit further tool use...

Direct source inspection confirms unconsented install-time credential harvesting and external exfiltration unrelated to an SDK. This is concrete malicious behavior, not merely a suspiciou...

Direct source inspection confirms unconsented install-time credential and file harvesting with external exfiltration to Telegram, unrelated to an OpenSea SDK. This is concrete malicious b...

Direct source inspection confirms an install-time lifecycle script performs unconsented credential, SSH key, wallet/seed, and environment secret exfiltration to Telegram. This is concrete...