npm detections from LPM Firewall.

Source inspection confirms runtime remote-code loading and browser proxy/service-worker behavior, while no install-time Node execution exists. The hidden remote loader and obfuscated cont...

Direct execution of an unpinned third-party script is a concrete remote-code-execution path in the package's runtime. The browser proxy/service-worker stack increases the impact, while ab...

No install-time execution was found, but the shipped browser entrypoint contains an immediate third-party payload load and a hard-coded remote proxy control path. Those behaviors establis...

The direct, unpinned external script import is concrete runtime attack behavior. The browser proxy and service-worker components compound the risk; absence of npm lifecycle hooks does not...

The remote executable dependency is unconditional in the package entry point, and the bundled service-worker proxy broadens its ability to handle browser traffic. Lack of npm lifecycle ex...

This is not merely obfuscated vendor code: the entry page directly delegates execution to an unrelated remote host and activates a cookie-aware proxy control plane. The absence of install...

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

No install-time hook runs, but the package's declared runtime entry directly executes an unrelated remote script and establishes a service-worker proxy that can process browsing traffic a...

This package is not a normal library entrypoint: its main artifact is a browser application that automatically executes a remote, unpinned script and ships an obfuscated proxy stack. The...

Direct source inspection confirms an automatic, unpinned third-party script loader in the browser entrypoint alongside obfuscated request-interception code. The absence of npm lifecycle h...

This is a concrete remote-code-execution supply-chain risk on normal package use, amplified by an embedded browser traffic-interception stack. Absence of npm lifecycle hooks does not miti...

This is a concrete remote-code-delivery chain activated by opening the package entrypoint, not merely a static heuristic. Lack of npm lifecycle hooks reduces install-time risk but does no...

The source confirms unconsented postinstall mutation of a global AI-agent extension/control surface and automatic installation of unrelated extensions. Although no exfiltration or destruc...

The direct external script tag is an immediate, unpinned remote payload loader, not merely an inert library reference. Combined with automatic service-worker proxy setup and pervasive obf...

This is not a benign library artifact: the package auto-executes third-party remote code and installs a browser request-routing proxy to unrelated infrastructure. No install hook is neede...

This is not an install-hook compromise, but it is a deliberately obfuscated static package whose primary entrypoint immediately delegates code execution to an unrelated remote host and co...

Direct source inspection confirms automatic remote-code execution and local obfuscated dynamic execution when the declared HTML entrypoint is opened. Absence of npm lifecycle hooks does n...

Source inspection confirms executable remote code loading and a persistent browser request-interception proxy tied to unrelated hosts. This is concrete harmful behavior despite the absenc...

The package has a concrete unconsented postinstall chain that mutates a broad, user-level AI-agent control surface and installs foreign extensions. No exfiltration was found, but the life...

Although installation itself has no lifecycle execution, the shipped browser entrypoint contains a concrete remote-code and request-interception chain. This exceeds a benign static-site p...