litclaude-ai@0.4.6
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has an automatic global postinstall registration path and a session-start self-update path that mutate Claude Code configuration. The code does not show a self-dependency, credential theft, or a non-package-aligned network endpoint, so this is a lifecycle risk rather than confirmed malware.
Decision evidence
public snapshot- A postinstall hook automatically runs the package installer during global npm installation.
- The installer modifies Claude Code's plugin registry, settings, HUD, and permission surface.
- A Claude Code session-start hook can trigger a foreground automatic update.
- The update path runs npm exec for a selected newer package version and backs up global Claude configuration files.
- The package contacts the npm registry to obtain update metadata.
- No runtime dependency on litclaude-ai is declared in package.json.
- The observed network endpoint is the npm registry and the response checks the expected package name.
- No credential collection or outbound secret transmission was found in the inspected lifecycle and update code.
Source & flagged code
17 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references dynamic require/import behavior.
scripts/qa-uiux-visual-qa-scenarios.mjsView on unpkg · L83Findings
Affected versions and remediation
This report applies to litclaude-ai@0.4.6.
See all versions of litclaude-ai for other recorded verdicts.
- Review the evidence and your use of litclaude-ai@0.4.6 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.