registry / ai-analyzer / 1.0.14

ai-analyzer@1.0.14

Usage: npx ai-analyzer analyze-phishing <file_path>

AI Security Review

scanned 2d ago · by lpm-firewall-ai

During npm installation, postinstall harvests local identity/system metadata, writes outside its package, and starts a detached process. Preinstall also contains an intended DNS request to an OAST host, though its undeclared os reference prevents execution as written.

Static reason

High-risk behavior combination matched malicious policy.

Trigger

npm install executes preinstall and postinstall

Impact

Unconsented installation-side system modification and persistence-like process creation; collected metadata is retained in temporary storage.

Mechanism

install-time host metadata collection, arbitrary file write, and detached-process creation

Attack narrative

Installing the package automatically runs postinstall. That script gathers host and user metadata plus Git identity, writes it to a temporary log, writes a test.exe to an absolute external path, and launches a detached sleep process. Its preinstall script attempts to construct a host-specific OAST request, but is broken by an undeclared os reference. The explicit CLI separately uploads user-selected file contents to the package service.

Rationale

The install hook performs unrelated host-data collection, external-path mutation, and detached-process creation without user consent. These concrete install-time behaviors warrant blocking even though the preinstall network attempt is defective.

Evidence

package.jsonpreinstall.jspostinstall.jsindex.jsbin/cli.js/mnt/user-data/outputs/test.exe<os.tmpdir()>/ai-analyzer-logs/postinstall-<timestamp>.json

Network endpoints

The preinstall lifecycle script in preinstall.js issues an HTTPS request whose hostname is constructed as os.hostname() prefixed to a hardcoded xstm5ywkgkh0fi1694d2u9ykbbh25vtk.oastify.com subdomain. oastify.com is PortSwigger's Burp Collaborator out-of-band canary service; DNS resolution of the constructed FQDN leaks the installer's hostname to the operator of that Collaborator instance at npm install time, together with host context (process.platform, process.version, process.cwd()). A companion postinstall.js writes hostname, username, homedir, proxy env vars, and git user.name/user.email to /tmp/ai-analyzer-logs/, producing a reconnaissance staging file on the installer's disk. The advertised library function analyzeEmail() unconditionally POSTs caller-supplied content to a hardcoded author-controlled endpoint at https://ai.calif-pentest.com/api/v1/ai-analyzer, with no caller-configurable destination — any consumer using the package's API silently forwards analyzed message content to that server. The calif-pentest.com branding and the Burp Collaborator beacon are consistent with an offensive-security actor. ## Source: ghsa-malware (a7bf033cf24a34d5e592f230dc374ebe62dd757f4f21c9eaa20613177e9becf9) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

ai-analyzer@1.0.14

AI Security Review

OSV Corroboration

Decision evidence

Source & flagged code

Source & flagged code

Findings

Source & flagged code