Which versions of ai-chat-helper are malicious?

The following npm versions of ai-chat-helper are flagged malicious: 1.0.1, 1.0.2, 1.0.9. Treat any of these as compromised.

How do I remediate ai-chat-helper if I installed it?

ai-chat-helper 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.

I already installed ai-chat-helper — how do I know if it already compromised me?

If ai-chat-helper 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.

Is ai-chat-helper part of a known attack campaign?

Yes — ai-chat-helper is associated with the IN-MAL-2026-006951, IN-MAL-2026-006952, IN-MAL-2026-006953 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find ai-chat-helper across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ai-chat-helper (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ai-chat-helper across your stack and pipelines.

Malicious package

ai-chat-helpernpm

ai-chat-helper is a confirmed malicious npm package (MAL-2026-6086) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.1, 1.0.2, 1.0.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ai-chat-helper (npm)

MAL-2026-6086

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall ai-chat-helper

What this malware does

collect.js performs system reconnaissance and exfiltration to a hardcoded attacker-controlled host. The script imports child_process, os, fs, http, and https; reads os.hostname(), os.homedir(), and inspects local filesystem paths via fs.existsSync; and POSTs the collected data to http://aab.sportsontheweb.net (line 13/line 366). The destination is an unrelated third-party domain over cleartext HTTP, with no relationship to any documented chat-helper functionality. This is the canonical credential/host-info beacon shape: child_process for command execution, os for host identity, fs for local file enumeration, and a hardcoded HTTP POST to an attacker domain.

Malicious versions

3 flagged

1.0.11.0.21.0.9

Indicators of compromise (SHA-256)

2a7654ff516176e3c9277ea8711149b1d55851165aa430307db43ebfdb578a3f

39a12d35a8713a8f63eaf342901214a7f53fa396b9ee8218d246e5e0db7b6318

6da659c2083db3bfaa683c19c572521b78359bbfb266ed9259192e19fe47e02f

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ai-chat-helper (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ai-chat-helper across your stack and pipelines.
If you installed it — respond
ai-chat-helper 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-chat-helper 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-chat-helper 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

No. ai-chat-helper on npm has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.0.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006951IN-MAL-2026-006952IN-MAL-2026-006953

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ai-chat-helper-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database