AI Security Review
scanned 21h ago · by lpm-firewall-aiThe package has an install-time hook that writes a fixed file under /tmp. No confirmed exfiltration, destructive action, remote payload loading, or AI-agent control hijack is present.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install lifecycle postinstall
Impact
Creates or overwrites /tmp/foo with static text during installation
Mechanism
install-time filesystem write
Rationale
This is suspicious because it mutates the host filesystem during postinstall without an evident package need, but the observed behavior is limited to a fixed /tmp file write and does not establish a malicious chain.
Evidence
package.jsonpostinstall.jsbin/tool.js/tmp/foo
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- package.json defines postinstall: node postinstall.js
- postinstall.js runs at install time and writes /tmp/foo
- postinstall.js performs filesystem mutation outside the package directory
Evidence against
- bin/tool.js only prints a greeting when invoked
- No network, credential access, shell execution, eval, dynamic loading, or agent control-surface writes found
- No dependency confusion or persistence mechanism found
Behavioral surface
Filesystem
Trivial
NoLicense
Source & flagged code
2 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
1 High1 Medium3 Low
HighInstall Time Lifecycle Scriptspackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
LowScripts Present
LowFilesystem
LowNo License