npm detections from LPM Firewall.

The package contains a concrete remote-code-execution chain, not merely network or process primitives. Absence of an install hook limits the trigger but does not mitigate runtime executio...

This is a concrete import-time remote-code-execution chain, not merely suspicious primitives. The hidden endpoint and token obfuscation, detached execution, and unrelated exported functio...

This is a concrete remote-code-execution chain unrelated to the declared package purpose. It is runtime-triggered rather than lifecycle-triggered, but remains malicious.

The unconditional remote script is sufficient concrete remote-code execution behavior at browser runtime; its behavior is not pinned or package-contained. Absence of lifecycle hooks reduc...

Direct source inspection confirms automatic remote code execution and service-worker proxy persistence when the package entrypoint is opened. These behaviors are unrelated to the package...

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...

Source inspection confirms automatic postinstall mutation of foreign, global AI-agent instruction surfaces. Under the install-control-surface policy, this is concrete malicious behavior r...

Direct inspection confirms unconsented postinstall mutation of multiple foreign/broad AI-agent configuration and instruction surfaces. The missing hook source limits one attempted hook pa...

No install hook executes during npm installation, but the declared browser entrypoint contains a concrete third-party remote-code execution path and an opaque request-interception stack....

This is not merely a scanner signal: the manifest points to `index.html`, which directly executes an arbitrary remote script. The remote execution is sufficient for a blocking malicious v...

This is not an inert library artifact: its entrypoint executes remote, operator-controlled code and includes browser request-interception infrastructure. Absence of npm lifecycle hooks do...

The direct page-load remote-code loader is a concrete staged execution path, not merely a static hint. Absence of npm lifecycle hooks limits install-time risk but does not remove runtime...

The unconditional remote executable script is a concrete externally controlled payload channel, and the bundled service-worker proxy infrastructure expands its browser-side interception c...

This is not an npm lifecycle attack, but the primary package artifact unconditionally executes a remote script from an unrelated host. The obfuscated browser bundle and request-proxy comp...

The package contains a concrete remote-code loader and automatic persistent browser traffic-routing mechanism unrelated to its declared package identity. Although it has no npm install ho...

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 Node compromise was found, but the runtime page automatically executes an unrelated third-party script and configures a service-worker proxy relay. The bundled obfuscation...

No install-time hook exists, but the shipped entrypoint directly executes unpinned remote code and installs a browser request-interception proxy that forwards request data to an unrelated...

No install-time host mutation occurs, but automatic unpinned third-party code execution is a concrete malicious supply-chain attack surface. Obfuscation and the bundled traffic-intercepti...

Source inspection confirms browser-side remote payload execution and a persistent service-worker proxy path, not merely scanner-observed obfuscation. Although installation itself has no l...