npm detections from LPM Firewall.

Concrete postinstall credential collection and transmission are present in source. The package should be blocked.

The postinstall hook contains concrete, unconsented command execution and credential-related environment harvesting with network forwarding. The benign runtime export does not mitigate th...

This is a concrete unconsented postinstall mutation of a foreign/broad AI-agent control surface. No separate exfiltration chain is needed for the blocking verdict.

This is concrete, unconsented postinstall mutation of foreign project-level AI-agent control files. The lack of exfiltration does not mitigate that policy-defined control-surface hijack.

This is concrete, obfuscated install/import-time metadata exfiltration, unrelated to the advertised utility package. The generic network helper does not mitigate the malicious DNS beacon.

Concrete install-time, obfuscated host-fingerprint exfiltration is present and unrelated to the advertised utility package. This is malicious behavior, not a benign network helper.

This is a concrete remote code-execution loader, not package-aligned icon functionality. Absence of an install hook does not mitigate the runtime execution path.

The public calendar helpers conceal an import-triggered downloader and Windows persistence routine unrelated to package functionality. This is malicious behavior despite a likely implemen...

The hidden import-time download, executable extraction, and Startup-folder persistence are concrete malware behavior unrelated to streak math. No lifecycle hook is needed because the payl...

The package is a concealed remote data-collection and input-automation tool unrelated to its stated system-binary configuration purpose. Although no install hook runs it automatically, ex...

The package establishes stealthy remote payload delivery and login persistence during ordinary import. Absence of an npm lifecycle hook does not mitigate this concrete runtime attack path.

This is a concrete remote payload and persistence mechanism unrelated to calendar/streak functionality. Absence of an npm lifecycle hook does not mitigate import-time execution.

Source shows a concrete runtime exfiltration path for sensitive account configuration to a non-service logging endpoint. This exceeds ordinary package telemetry and is not install-time de...

The third-party logging endpoint receives sensitive account configuration without a user-facing consent boundary. No install hook is needed for this runtime exfiltration to be malicious.

Source inspection confirms a concealed remote-code-execution path in src/index.cjs. It is not install-time, but it is concrete malicious functionality rather than a package-aligned feature.

The native addon’s imported APIs and embedded anti-analysis/staging indicators are materially inconsistent with a buffer utility. The absence of install hooks does not mitigate import-tim...

Direct inspection confirms default runtime cookie exfiltration unrelated to icon rendering. No install hook is needed for this concrete malicious behavior.

Direct source inspection confirms runtime cookie exfiltration to external endpoints; no install hook is required for the malicious behavior.

Concrete source shows automatic, suppressed transmission of mail/account-related logs to an unrelated remote endpoint. The benign workspace-only postinstall hook does not mitigate this ru...

Despite no npm lifecycle hook, the default import path performs concealed, import-time cross-platform startup persistence by dropping a native executable. This is concrete malicious behav...

This is a concrete unconsented postinstall mutation of a broad AI-agent control surface. Absence of exfiltration does not remove the persistent prompt/control hijack risk.