malware-catnip
Benign, educational install-hook demonstrator for testing software supply-chain dependency/install-script detection. Not malware.
This report shows the evidence for malware-catnip@1.0.2, the only known version.
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe automatic lifecycle hook launches six unsolicited browser windows and detaches its process, creating disruptive behavior on installation. The README's self-description as a benign scanner fixture does not excuse that behavior.
Decision evidence
public snapshot- The manifest automatically runs preinstall.js during installation.
- The install hook detaches a background copy so its activity continues after the hook exits.
- The script creates a local autoplay page for a bundled video and schedules six browser windows.
- The README presents the package as a benign security testing sample, which is self-asserted package text.
- The inspected script uses a bundled video and local file URL; it contains no network endpoint.
- The visible behavior is limited to opening browser windows and creating files within the package directory.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe manifest automatically runs preinstall.js during installation.
package.jsonView on unpkg · L15Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to malware-catnip@1.0.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing malware-catnip@1.0.2. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.