What does the chat-adapter-matrix malware do?

chat-adapter-matrix@99.99.99 executes server.js from every npm lifecycle hook (preinstall, install, postinstall, prepare, prepublish, preprepare, postprepare) and from the main module. server.js issues an HTTPS GET to the hardcoded webhook host eo8f3m3ho26a0nm.m.pipedream.net with the package name embedded in the URL path (https://eo8f3m3ho26a0nm.m.pipedream.net/vercel/ ). The receiving Pipedream endpoint captures the source IP, hostname context, and confirmation that this squatted name was resolved and installed. The implausibly high 99.99.99 version and the embedded 'Proof by @0xWise' string are consistent with a dependency-confusion payload designed to win version resolution against a

Which versions of chat-adapter-matrix are malicious?

The following npm versions of chat-adapter-matrix are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate chat-adapter-matrix if I installed it?

chat-adapter-matrix establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed chat-adapter-matrix — how do I know if it already compromised me?

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

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

Malicious package

chat-adapter-matrixnpm

chat-adapter-matrix is a confirmed malicious npm package (MAL-2026-16308) that opens a backdoor for remote access (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chat-adapter-matrix (npm)

MAL-2026-16308

Immediate action

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

npm uninstall chat-adapter-matrix

What this malware does

[email protected] executes server.js from every npm lifecycle hook (preinstall, install, postinstall, prepare, prepublish, preprepare, postprepare) and from the main module. server.js issues an HTTPS GET to the hardcoded webhook host eo8f3m3ho26a0nm.m.pipedream.net with the package name embedded in the URL path (https://eo8f3m3ho26a0nm.m.pipedream.net/vercel/<pkg>). The receiving Pipedream endpoint captures the source IP, hostname context, and confirmation that this squatted name was resolved and installed. The implausibly high 99.99.99 version and the embedded 'Proof by @0xWise' string are consistent with a dependency-confusion payload designed to win version resolution against an internal package of the same name and beacon successful installs on internal build systems to the researcher/attacker's collector.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

5710eb2e1a2f6b7a4aca8d943953989e80e056cc77c2071027c2a78744b5ea3a

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chat-adapter-matrix (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chat-adapter-matrix across your stack and pipelines.
If you installed it — respond
chat-adapter-matrix establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If chat-adapter-matrix 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 chat-adapter-matrix 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. chat-adapter-matrix on npm has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020198

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks chat-adapter-matrix-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database