MalwarePublished 10 Jul 2026Updated 14 Jul 2026

stella-coder (npm) · Malicious Code

Affects stella-coderSource GCVE Database

Malicious package : remove stella-coder and rotate any secrets on hosts that installed it.

Data as of 14 Jul 2026, 09:27 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-10134

What to do

Remove stella-coder from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmstella-coder	Affected 4.0.0 – 5.1.2 6 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (f0c3ed879ef15a68d537ad7b6ddb59508aba58eee49c8ca19b916ef59a0c2da6) stella-cli/telegram-bot.mjs hardcodes a Telegram bot API token (BOT_TOKEN = "8923551485:AAFw4wG8ZwOtp5rzFsnguxhu4AH-2_ebSi0") that is controlled by the package author. When the user invokes the /tg CLI command, the package starts a Telegram bot on the installer's machine that receives messages over api.telegram.org and passes them into execSync(`node stella-cli/index.mjs -p "${text}"`), invoking a shell-capable AI agent CLI with attacker-supplied input. Because the messaging channel is bound to a token the author retains, the author observes all bot traffic — including the 4-digit admin authorization code exchanged over that same channel — and can replay it to reach the command-execution path on any installer that enables /tg. telegram-bot.mjs additionally sends os.hostname() and os.userInfo().username to the same author-controlled bot. A hardcoded PREMIUM_CODE = "10102013" acts as a universal activation key that unlocks the remote-control feature-set without payment. package.json sets "main": "stella-cli/index.mjs", whose top-level executes main() and starts the interactive CLI on require/import, extending the reach of the /tg surface beyond the bin entry. There are no install lifecycle hooks; the backdoor fires when the user runs the CLI (or a consumer imports the module) and invokes /tg.

Impact

This malicious package enables remote code execution on the installer's machine via a Telegram bot controlled by the package author. The attacker can execute arbitrary shell commands, potentially compromising the entire system. Sensitive information such as hostname and username is exfiltrated to the attacker. The presence of a universal activation key allows the attacker to activate the backdoor without payment. This represents a severe compromise of confidentiality, integrity, and availability for users who run the /tg command or import the module and invoke this functionality.

Defensive guidance

Users should immediately discontinue use of the affected stella-coder versions (4.0.0, 5.0.0, 5.0.1, 5.1.0, 5.1.1, 5.1.2) and remove the package from their environments. Avoid running the /tg CLI command or importing the module in a way that triggers this functionality. Monitor for any updates from the package author or npm registry for potential fixes or removal of the malicious code. Consider using trusted alternatives and verifying package integrity before installation.

Summary

The stella-coder npm package contains a backdoor implemented via a hardcoded Telegram bot API token. This token allows the package author to control a Telegram bot running on the installer's machine. When the user runs the /tg CLI command, the bot receives messages from the attacker and executes them as shell commands through a node subprocess. The attacker can intercept and replay an admin authorization code to gain command execution on any machine running the package with the /tg feature enabled. Additionally, the package leaks system information (hostname and username) to the attacker. The malicious code is triggered by running the CLI or importing the module and invoking /tg. A hardcoded universal activation key bypasses payment requirements for the remote control feature. The affected versions are explicitly 4.0.0, 5.0.0, 5.0.1, 5.1.0, 5.1.1, and 5.1.2.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Jul 2026, 10:05 UTC

Technical details

References

Community reviews