npm detections from LPM Firewall.

Concrete install-time execution of an obfuscated credential-harvesting payload establishes malicious behavior. The legitimate-looking UI bundles do not mitigate the preinstall attack path.

The benign lint-rule entrypoint does not justify the preinstall bootstrap or its obfuscated token-oriented payload. This is concrete malicious install-time behavior.

The install hook executes a concealed, unrelated payload with remote eval and GitHub-token handling; this is concrete malicious behavior, not package-aligned setup.

This is concrete install-time staged execution followed by credential-harvesting behavior, not a package-aligned build step. The benign component source does not justify the hidden preins...

This is concrete unconsented install-time credential theft and remote code execution, not a package-aligned build step. The visible theme code does not justify the concealed preinstall ch...

The concealed preinstall chain executes an obfuscated token-oriented payload and is concrete malicious behavior. The visible UI source does not justify this install-time functionality.

The preinstall chain executes a concealed payload rather than package functionality, with remote eval and token handling. This is concrete malicious install-time behavior.

Concrete preinstall execution, downloader behavior, obfuscation, and runtime eval establish malicious install-time remote code execution.

The package has an unconsented preinstall chain that bootstraps a runtime solely to execute a large obfuscated, credential/network-capable payload. This is concrete malicious install-time...

The lifecycle chain concretely executes a concealed credential-oriented network payload at install time. Its behavior is unrelated to the package’s stated library functionality.

The install-time loader is unrelated to the declared chart package and creates a concrete remote-code-execution chain with credential-access capability.

The lifecycle script is unrelated to the advertised visualization package and deliberately bootstraps an interpreter for an obfuscated payload. Its fetched-content eval and token-oriented...

This is concrete, unconsented install-time remote payload execution, not normal component-kit behavior. The benign UI source does not mitigate the lifecycle attack path.

The lifecycle payload is materially unrelated to the advertised package and establishes remote code execution at install time. Obfuscation and credential-token logic reinforce malicious i...

The package contains a concrete, unconsented preinstall remote-code-execution chain. The benign CLI does not justify the obfuscated secondary payload.

This is concrete unconsented install-time execution, not an application-aligned dependency helper. The obfuscated payload's credential collection, exfiltration flow, and remote eval estab...

The malicious preinstall chain executes an obfuscated payload with credential-oriented and network behavior. The legitimate bundled component code does not justify it.

Source inspection confirms a concealed, dynamically evaluated payload executed automatically at install time, with GitHub credential-token handling. This is concrete malicious behavior, n...

The lifecycle hook is unrelated to a React UI library and deliberately stages an obfuscated payload. Direct source inspection confirms credential collection and remote content evaluation.

The preinstall chain is unrelated to a chart-theme library and deliberately stages an obfuscated, remotely extensible credential-capable payload. This is concrete malicious install-time b...

The concrete preinstall chain downloads/executes a runtime and evaluates network-delivered code. This is not required by the declared chatbot UI entrypoint and constitutes malware behavior.