Which versions of @chat-components/common are malicious?

The following npm versions of @chat-components/common are flagged malicious: 0.0.1, 0.0.2. Treat any of these as compromised.

How do I remediate @chat-components/common if I installed it?

Remove @chat-components/common 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 @chat-components/common — how do I know if it already compromised me?

If @chat-components/common 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-components/common part of a known attack campaign?

Yes — @chat-components/common is associated with the RLMA-2025-02637, RLUA-2025-06015 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-components/common 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-components/common (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @chat-components/common across your stack and pipelines.

Malicious package

@chat-components/commonnpm

@chat-components/common is a confirmed malicious npm package (MAL-2025-3958) that executes malicious code on install (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @chat-components/common (npm)

MAL-2025-3958

Immediate action

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

npm uninstall @chat-components/common

What this malware does

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

68ce52297a40a21276b5a4ea27d07c7b351beefe4e25c0682e3daf848a0ddc5c

58618727a31c363b0a52da42ea351c06fe341315f0a2adcb2097c291e0ebb874

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 @chat-components/common (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @chat-components/common across your stack and pipelines.
If you installed it — respond
Remove @chat-components/common 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 @chat-components/common 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-components/common 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-components/common on npm has been identified as a malicious package (versions 0.0.1, 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-02637RLUA-2025-06015

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @chat-components/common-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

Explore

All malware advisories How O3 detects malware Vulnerability database