Which versions of chatbotloader are malicious?

The following npm versions of chatbotloader are flagged malicious: 9999.1.0. Treat any of these as compromised.

How do I remediate chatbotloader if I installed it?

Remove chatbotloader 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 chatbotloader — how do I know if it already compromised me?

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

Yes — chatbotloader is associated with the GHSA-g7q7-rf3f-vw4h, RLMA-2026-01924 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 chatbotloader 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 chatbotloader (version 9999.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chatbotloader across your stack and pipelines.

Malicious package

chatbotloadernpm

Malicious code in chatbotloader (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2642

Immediate action

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

npm uninstall chatbotloader

What this malware does

The package chatbotloader was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

9999.1.0

Indicators of compromise (SHA-256)

88ccdb3c34d69b2e53f62caa6b7e61f32e7868fa5893d6fd6d09662189d10b34

639423fe0934d863fc3c72189cde2e0fe020174d43fb7db9da4cc8b8e52bf7b3

78643cb5d37687c0eac0935734bac95f23c01b64ded6bb2f2f090542324042ac

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

Campaign

GHSA-g7q7-rf3f-vw4hRLMA-2026-01924

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks chatbotloader-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