ai-analyzernpm
ai-analyzer is a confirmed malicious npm package (MAL-2026-13934) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.14, 1.0.15, 1.0.16…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ai-analyzer (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ai-analyzer (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ai-analyzer across your stack and pipelines.
If you installed it — respond
ai-analyzer is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If ai-analyzer was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks ai-analyzer before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks ai-analyzer-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.