npm persistence and destructive behavior reports.
Investigate persistence and destructive actions, including unwanted lasting changes, damaged files, and disrupted systems. These reports include LPM Firewall detections. Each report identifies the package version, supporting evidence, advisory sources, and current Firewall decision.
Security reports — page 4
Updated Nov 22, 2026, 13:02 UTC · newest scans first
The manifest contains a concrete destructive pack-time action that removes nearly every entry in its own package directory.
The postpack hook contains a concrete destructive action against the package directory, so this is malicious rather than a clean result. The trigger is packaging, not consumer installation.
The automatic postpack hook recursively deletes nearly the entire package directory, creating a concrete destructive action when packing is invoked.
The undocumented, import-time hidden launch and directory watch establish a concrete covert execution chain. The lack of a network sink does not remove the local execution and staging risk.