tt-help-cli-ycl (npm) · Malicious Code
Affects tt-help-cli-yclSource GCVE Database
Malicious package : remove tt-help-cli-ycl and rotate any secrets on hosts that installed it.
Data as of 8 Aug 2026, 14:53 UTC
Malicious package
Published to npm · OSV MAL-2026-12488
What to do
Remove tt-help-cli-ycl 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 |
|---|---|---|
| npmtt-help-cli-ycl | Affected
| 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 (e6144be61d70f258741e5d4cc1476021f93e3ce82ffa00a3f86189537a1438a6) The package's `tt-help watchdog` subcommand starts a long-running agent that POSTs heartbeats to a remote server (default hardcoded to http://117.71.53.99:17301, referenced in src/lib/constants.js and the README/run-explore examples) and executes commands returned in the response. In WatchdogAgent, syncCommands maps entries from the server's `commands` array into child_process.spawn(command, { shell: true }) via ProcessManager.startCommand, with auto-restart — the remote operator selects arbitrary shell commands to run on the installer's host. Each heartbeat body assembled by _buildHeartbeatBody carries hostname, non-internal IPv4 address, OS platform/release/arch, CPU count, memory, node version, uptime, load average, and the contents of ~/.tt-help.json (server, proxy, browser, userId, tuning fields), POSTed as JSON to ${serverUrl}/api/watchdog/heartbeat at the configured interval (default 15s). In addition, _startUpgradeChecker polls the npm registry every 10 minutes and, when a new version of tt-help-cli-ycl is published, invokes `npm install -g tt-help-cli-ycl@latest` via child_process.exec and re-spawns, so the publisher can push arbitrary new code to every running agent host without user confirmation. The combination of remote-command execution, ongoing host inventory + stored-config exfiltration to a bare-IP destination, and unattended auto-upgrade constitutes a full command-and-control backdoor rather than a legitimate remote-management tool.
References
- npmjs.com/package/tt-help-cli-ycl/v/1.4.61 (opens in a new tab)
- npmjs.com/package/tt-help-cli-ycl/v/1.4.59 (opens in a new tab)
- npmjs.com/package/tt-help-cli-ycl/v/1.4.60 (opens in a new tab)
- npmjs.com/package/tt-help-cli-ycl/v/1.4.63 (opens in a new tab)
- npmjs.com/package/tt-help-cli-ycl/v/1.4.64 (opens in a new tab)
- npmjs.com/package/tt-help-cli-ycl/v/1.4.67 (opens in a new tab)
- npmjs.com/package/tt-help-cli-ycl/v/1.4.71 (opens in a new tab)
- npmjs.com/package/tt-help-cli-ycl/v/1.4.65 (opens in a new tab)
- npmjs.com/package/tt-help-cli-ycl/v/1.4.70 (opens in a new tab)
- npmjs.com/package/tt-help-cli-ycl/v/1.4.66 (opens in a new tab)
- npmjs.com/package/tt-help-cli-ycl/v/1.4.57 (opens in a new tab)
- npmjs.com/package/tt-help-cli-ycl/v/1.4.73 (opens in a new tab)
- npmjs.com/package/tt-help-cli-ycl/v/1.4.62 (opens in a new tab)
- npmjs.com/package/tt-help-cli-ycl/v/1.4.69 (opens in a new tab)
- npmjs.com/package/tt-help-cli-ycl/v/1.4.72 (opens in a new tab)
- npmjs.com/package/tt-help-cli-ycl/v/1.4.58 (opens in a new tab)
- npmjs.com/package/tt-help-cli-ycl/v/1.4.68 (opens in a new tab)
- npmjs.com/package/tt-help-cli-ycl/v/1.4.74 (opens in a new tab)
- npmjs.com/package/tt-help-cli-ycl/v/1.4.78 (opens in a new tab)
- npmjs.com/package/tt-help-cli-ycl/v/1.4.75 (opens in a new tab)