Which versions of xy-ai-chat are malicious?

The following npm versions of xy-ai-chat are flagged malicious: 0.0.34, 0.1.1. Treat any of these as compromised.

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

Remove xy-ai-chat from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

If xy-ai-chat 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 xy-ai-chat part of a known attack campaign?

Yes — xy-ai-chat is associated with the IN-MAL-2026-004153, IN-MAL-2026-004155 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 xy-ai-chat 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 xy-ai-chat (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging xy-ai-chat across your stack and pipelines.

Malicious package

xy-ai-chatnpm

Malicious code in xy-ai-chat (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4735

Immediate action

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

npm uninstall xy-ai-chat

What this malware does

xy-ai-chat ships a Lit web component (<ai-chat-element>) whose bundled main entry hardcodes two plain-HTTP endpoints on a bare IPv4 address: http://182.43.87.39:9050/polymerize and http://182.43.87.39:9062/chat-ai-app-message/saveByUser. The latter path name (saveByUser) and the surrounding fetch() calls in dist/index.esm.js (lines 9774, 9835) indicate that end-user chat content typed into the component is POSTed to the author-controlled server with no configurability exposed in the component's API. Any site embedding this component routes its end users' chat input to that destination, with no TLS (plain HTTP, so any on-path observer also sees the content), no domain (so the destination cannot be rotated or audited via DNS/CA infrastructure), and no opt-in. The package.json has no homepage or publisher metadata identifying who operates 182.43.87.39. This is the silent-relay shape: the package's advertised API silently siphons caller-supplied data to a hardcoded third-party destination.

Malicious versions

2 flagged

0.0.340.1.1

Indicators of compromise (SHA-256)

5461a3afe83eecc08c4f9e2413d1c0a92c6e34cbeea1de89d0798bc389d2d652

5f9025a3fddb0d31a5cd9114850b0ca859acf96e54649d4d2a9fe286b7ca015c

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for xy-ai-chat (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging xy-ai-chat across your stack and pipelines.
If you installed it — respond
Remove xy-ai-chat from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If xy-ai-chat 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 xy-ai-chat 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. xy-ai-chat on npm has been identified as a malicious package (versions 0.0.34, 0.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004153IN-MAL-2026-004155

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks xy-ai-chat-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring