registry / Data exfiltration / ai-analyzer
ai-analyzer
Usage: npx ai-analyzer analyze-phishing <file_path>
This report shows the evidence for ai-analyzer@1.0.19. 20 of 21 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe preinstall network requests exfiltrate machine and account identifiers without a user command or package functionality justification. This is concrete install-time data exfiltration.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
npm preinstall and postinstall lifecycle execution
Impact
Leaks installer host and account identifiers before installation completes; stages further collected data locally.
Mechanism
install-time system-identity collection and network exfiltration
Attack narrative
During npm preinstall, the package constructs HTTPS hostnames containing the local hostname and username under notifyme.calif-int.org and requests them, exposing those identifiers to the endpoint operator. Its postinstall script gathers additional system, proxy, registry, and Git identity data and records it in a temporary file. Separately, its CLI uploads user-selected file content to a remote API.
AI rationale
The preinstall network requests exfiltrate machine and account identifiers without a user command or package functionality justification. This is concrete install-time data exfiltration.
Evidence
package.jsonpreinstall.jspostinstall.jsindex.js$TMPDIR/ai-analyzer-logs/postinstall-<timestamp>.json
Network endpoints2
.notifyme.calif-int.orgai-analyzer.notifyme.calif-int.org/api/v1
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- Install lifecycle runs preinstall.js and postinstall.js.
- Preinstall makes HTTPS requests to attacker-controlled subdomains derived from hostname and username.
- Postinstall harvests host, account, path, proxy, registry, and Git identity data.
- Postinstall writes harvested installation data to a temporary log file.
- CLI sends user-selected file contents to a remote API.
Evidence against
- Postinstall has no direct network transmission in this source.
- CLI file upload requires an explicit user command.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
UrlStrings
Source & flagged code
6 flagged · loading sourcepackage.jsonView file
•scripts.preinstall = node preinstall.js 2>/dev/null || node -e "console.log('Pre-install check')"
Critical
Red Install Lifecycle Script
Install-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkg•scripts.preinstall = node preinstall.js 2>/dev/null || node -e "console.log('Pre-install check')"
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg13"prepare": "echo 'Prepare script executed' && exit 0",
"preinstall": "node preinstall.js 2>/dev/null || node -e \"console.log('Pre-install check')\"",
"postinstall": "node postinstall.js 2>/dev/null || true"
High
Suspicious Lifecycle Evidence
Install lifecycle runs preinstall.js and postinstall.js.
package.jsonView on unpkg · L13•scripts.postinstall = node postinstall.js 2>/dev/null || true
Findings
1 Critical4 High3 Medium4 Low
CriticalRed Install Lifecycle Scriptpackage.json
HighInstall Time Lifecycle Scriptspackage.json
HighKnown Malware Source Similaritypostinstall.js
HighSuspicious Lifecycle Evidencepackage.json
HighAi Review Evidencepreinstall.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowUrl Strings
Affected versions and remediation
This report applies to ai-analyzer@1.0.19.
The versions list below shows the verdict for each recorded version.
- Avoid installing ai-analyzer@1.0.19. 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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.