lc-chatbotnpm
Advisory published Updated
lc-chatbot is a confirmed malicious npm package (MAL-2026-6559) that steals credentials and exfiltrates sensitive data (malicious version 0.9.0-rc.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in lc-chatbot (npm)
What this malware does
package.json declares both preinstall and postinstall scripts that run node callback.js, so the callback fires automatically on npm install with no user interaction. callback.js collects identifying data from the installer's machine — os.hostname(), os.userInfo().username, process.cwd(), the consuming package name@version, and process.platform/arch — and transmits it to two attacker-controlled collectors: (1) a DNS lookup whose label is the hex-encoded hostname under a canarytokens.com subdomain, and (2) an HTTPS GET to https://eolxuw8fddeyjj8.m.pipedream.net carrying the collected fields as query parameters. The callback wraps all I/O in try/catch and forces process.exitCode=0, so the install completes silently even if the network call fails, hiding the beacon from the installer. The package self-describes as a dependency-confusion proof-of-concept, but the behavior is genuine install-time exfiltration of installer-identifying data and harms any machine that runs npm install.
The OpenSSF Package Analysis project identified 'lc-chatbot' @ 0.9.0-rc.0 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for lc-chatbot (version 0.9.0-rc.0).
If you installed it — respond
lc-chatbot 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 lc-chatbot was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks lc-chatbot-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.