npm credential and data exfiltration reports.

Source directly implements automatic environment harvesting and external transmission during npm install. The malformed hostname may prevent delivery, but does not negate the concrete mal...

This is not an install-hook-only finding: the malicious payload is reached by an ordinary import. Its concealed host collection and outbound transmission are incompatible with the package...

Direct inspection confirms a concrete install-time data-exfiltration chain with no apparent package-aligned functionality. This is malicious behavior, not merely a suspicious primitive.

Source inspection confirms concrete preinstall-time collection and external transmission of local/CI metadata. The behavior is unrelated to the package's empty runtime export and is malic...

Source inspection confirms an unconsented install-time telemetry/exfiltration chain rather than a benign user-invoked monitoring feature. The lifecycle script collects a public IP and sen...

The install hook performs concrete network collection and remote reporting rather than a package-aligned build/setup task. Its hardcoded destination and forced demo event make the behavio...

Source inspection confirms concrete automatic install-time metadata exfiltration to an unrelated external endpoint. This is malicious behavior, not a benign package setup action.

Source confirms a concrete credential-exfiltration chain, not merely scanner heuristics. The install-time workflow setup is secondary and does not mitigate the silent credential upload.

Direct inspection confirms concrete hidden privileged access and outbound telemetry unrelated to user configuration. The lack of lifecycle hooks does not mitigate the runtime backdoor onc...

Direct inspection confirms concrete, automatic credential exfiltration in the package manifest. This is not package-aligned functionality and meets the blocking threshold.

Direct inspection of the sole shipped file confirms concrete install-time credential harvesting and external exfiltration. This is malicious behavior, not a package-aligned feature.

Static source inspection confirms unconsented install-time and import-time environment harvesting followed by network transmission. Conditional backend configuration does not remove the c...

Direct source inspection confirms unconsented postinstall credential harvesting and remote exfiltration. This is concrete malicious behavior, not a scanner-only inference.

Direct inspection confirms install-time collection and remote transmission of the installer environment. No legitimate package functionality is present to justify this behavior.

Direct inspection of the sole package file confirms an install-time credential-harvesting payload with third-party network exfiltration. This is malicious behavior, not a package-aligned...

Direct inspection of the sole packaged file confirms automatic install-time credential harvesting and external exfiltration. This is concrete malicious behavior, not a scanner-only infere...

This is concrete, unconsented install-time credential exfiltration, not merely a user-invoked secrets utility. The configurable endpoint does not remove the risk because the package autom...

Direct source inspection confirms credential collection and exfiltration, not merely suspicious primitives. The lack of an install lifecycle hook limits the trigger to import/execution bu...

This is concrete credential exfiltration and remote-control behavior, not merely a dormant capability. The lack of install hooks reduces install-time risk but does not mitigate the explic...

Source directly implements credential harvesting and remote transmission of reusable Lark secrets. The user-facing telemetry and Digital Worker paths make this behavior concrete despite t...

Direct source inspection confirms an unconsented install-time exfiltration request. The empty entrypoint makes the telemetry behavior clearly malicious rather than package-aligned.