npm detections from LPM Firewall.

The source confirms an unconsented postinstall mutation of broad, foreign AI-agent control surfaces. No separate exfiltration or payload execution was found, but the install-time control-...

This meets the blocking policy: an npm postinstall mutates broad foreign AI-agent control surfaces without an explicit user setup command. The remote executable delivery chain materially...

This is a concrete remote-command and sensitive-data collection channel, not merely a local automation primitive. Lack of an install hook reduces install-time risk but does not remove the...

Source establishes an automatic remote-payload-to-execution chain with no user invocation or integrity verification. This is concrete malware behavior, not ordinary telemetry.

This is concrete import-time staged payload execution, not normal telemetry: opaque remote binaries are fetched, dropped, and executed without user action. The same behavior is also imple...

This is concrete unconsented postinstall mutation of a shared, foreign AI-agent credential/control surface, coupled with silent account provisioning and credential replacement. The behavi...

This is a concrete import-time remote-code-execution chain, not ordinary telemetry. No lifecycle hook is needed because index.js reaches the loader whenever consumers import the package.

This is a concrete, import-triggered remote code execution chain with concealed payload delivery and detached execution. The absence of npm lifecycle scripts does not mitigate the runtime...

The import-time bridge is a concrete staged malware loader, independent of npm lifecycle scripts. The telemetry module also implements a similar configurable native-extension loader.

The import-time remote download-and-execute chain is concrete source behavior, not a scanner-only inference. It is unrelated to the package's stated TypeScript-definition purpose.

Source directly confirms an automatic staged payload downloader and executor at the package entrypoint. The lack of install hooks does not mitigate runtime import-time execution.

This is a concrete import-time remote native payload execution chain, not normal telemetry. The lack of lifecycle hooks does not mitigate execution when consumers import the package.

This is a concrete import-time remote-code-execution chain with no integrity verification and concealment through fragmented strings, rotating hosts, temporary filenames, and suppressed e...

This is concrete, unconsented postinstall mutation of multiple foreign AI-agent control surfaces. Package-aligned downloading does not mitigate the control-hijack behavior.

This is a concrete, import-triggered remote payload execution chain with obfuscated endpoints and no payload validation. It is unrelated to the declared API-client purpose.

The source provides a concrete, automatically reachable remote payload download-and-execute chain, not merely telemetry behavior. Lack of an install hook does not mitigate execution on no...

This is concrete, automatically reachable remote native-code execution, not telemetry functionality. Lack of an install hook does not mitigate the import-time execution path.

This is a concrete import-time remote-code-execution chain disguised as analytics/profiling. Absence of an npm lifecycle hook does not mitigate runtime execution when the package is impor...

This is a concrete import-time remote-code-execution chain, not ordinary telemetry. The telemetry module contains a similarly capable configurable downloader, reinforcing the malicious pa...

This is a concrete, automatically reachable remote-code-execution chain disguised as analytics/telemetry. The lack of an npm lifecycle script does not mitigate import-time execution.

This is concrete import-time remote code execution, not legitimate telemetry: the fetched opaque payload is directly executed without verification. No install hook is needed because ordin...