npm detections from LPM Firewall.

Source directly establishes unconsented postinstall mutation of broad, foreign AI-agent control surfaces, meeting the blocking policy. The package-aligned download and local credential ha...

The import-time loader establishes a concrete staged-payload execution chain; the lack of an npm lifecycle hook does not mitigate runtime compromise.

This is a concrete import-triggered remote payload execution chain unrelated to the advertised UI package. Lack of lifecycle hooks does not mitigate the malicious runtime side effect.

The package contains concrete, stealthy import-time remote payload execution unrelated to its stated mobile payment-widget purpose. This is malicious despite the absence of lifecycle hooks.

The package entrypoint contains an import-time, obfuscated downloader/executor with no legitimate API relationship to the declared foundational-types package. This establishes concrete ma...

The package's ordinary import path implements an obfuscated, unverified remote native-payload execution chain unrelated to its stated SDK purpose. This is concrete malware behavior, not m...

Source directly establishes an import-time downloader/dropper/executor chain. The lack of lifecycle hooks does not mitigate execution on normal package use.

This is a concrete import-time remote payload execution chain unrelated to the documented foundational-types API. The lack of an npm lifecycle hook does not mitigate runtime execution on...

This is concrete import-time remote code execution, disguised as telemetry compatibility behavior. The lack of an install hook does not mitigate execution when any consumer imports the pa...

The package's advertised checkout-parameter API does not require a silent native downloader. Its import-time remote payload execution is concrete malicious behavior.

The package has no install hook, but normal import directly activates remote payload retrieval and execution. This is concrete malware behavior, not a benign telemetry primitive.

The malicious loader is import-reachable from the declared main entrypoint and executes opaque remote content without verification. Lack of install hooks does not mitigate runtime arbitra...

This is a concrete import-time remote-payload execution chain, not legitimate shared primitives or telemetry. Lack of an npm lifecycle hook does not mitigate execution when an application...

The package’s only public entrypoint executes a concealed remote payload chain with no user action beyond importing it. No legitimate wrapper functionality explains binary retrieval and d...

This is concrete import-time remote code execution, not legitimate telemetry: the downloaded bytes are executed without validation and are concealed behind a benign wrapper.

This is a concrete import-time remote payload execution chain with obfuscated endpoints and no integrity verification. The lack of lifecycle hooks does not mitigate execution when the adv...

The package performs concrete import-time staged payload delivery and detached execution, which is remote code execution rather than legitimate loader functionality.

This is a concrete import-time staged-payload chain culminating in detached arbitrary native-code execution, unrelated to the advertised lazy-loader interface.

This is concrete import-time remote code execution, not package-aligned telemetry. The unused telemetry file contains a similar downloader pattern but does not mitigate the active _shim.j...

The import-time loader provides unconsented remote payload execution unrelated to the advertised token-map API. Lack of install hooks does not mitigate the reachable runtime execution path.

This is a concrete, silent import-time remote payload execution chain unrelated to the declared select-user library. Absence of npm lifecycle hooks does not mitigate the reachable runtime...