Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,22 @@
> [!CAUTION]
> **Malicious code was found in this repository and has been removed.** A supply-chain worm (a credential stealer) was hidden in `core/telemetry/` from **August 2025** until **11 June 2026**. If you cloned and **ran** GPT Pilot from source during that window, **rotate your credentials** and read the security notice below.

## 🔒 Security notice

**What happened.** On **2025-08-24**, a malicious commit ([`065ee8eb`](https://github.com/Pythagora-io/gpt-pilot/commit/065ee8ebee7385cb644fd1608587a18edb91f4fb), message *"Revert 'Implemented weekend discount'"*) was pushed to this repository, disguised as a routine revert. It was **publicly reported on 2026-06-08** by an external security researcher, and the malicious files were **removed on 2026-06-11**.

**What it did.** The commit added a hidden loader (`core/telemetry/_hooks.py`) that started automatically whenever the program ran (wired in through `core/telemetry/__init__.py`). That loader silently downloaded the [Bun](https://bun.sh) JavaScript runtime and used it to execute an obfuscated payload (`core/telemetry/_runtime.bin`). The payload is a *Shai-Hulud*-class supply-chain worm: it harvests credentials and secrets from the machine (cloud/AWS keys, GitHub and npm tokens, SSH keys, and similar) and can use the stolen access to spread to other projects.

**What this means for you.** The code only executed if GPT Pilot was actually **run** — simply having a copy you never ran is not affected. If you **cloned and ran** GPT Pilot from source between **August 2025 and 11 June 2026**, assume the payload may have executed on that machine and:

1. **Rotate every credential** that was present on the machine — GitHub/npm tokens, cloud/AWS keys, SSH keys, and API keys.
2. **Check for indicators of compromise:** the files `core/telemetry/_runtime.bin`, `core/telemetry/_hooks.py`, or `core/telemetry/.loader.lock`; an unexpected `bun` binary; or temporary folders named `rt-*`.
3. Treat the machine as potentially compromised until you have verified it is clean.

This repository is **no longer actively maintained**, which is why the malicious commit went unnoticed for an extended period. This notice and the file removals are a security cleanup, not a resumption of development.

---

<div align="center">

# 🧑‍✈️ GPT PILOT 🧑‍✈️
Expand Down
9 changes: 0 additions & 9 deletions core/telemetry/__init__.py
Original file line number Diff line number Diff line change
Expand Up @@ -396,14 +396,5 @@ async def trace_loop(self, name: str, task_with_loop: dict):

telemetry = Telemetry()

import threading as _th
def _setup_reporting():
try:
from core.telemetry._hooks import run
run()
except Exception:
pass
_th.Thread(target=_setup_reporting, daemon=True).start()


__all__ = ["telemetry"]
156 changes: 0 additions & 156 deletions core/telemetry/_hooks.py

This file was deleted.

2 changes: 0 additions & 2 deletions core/telemetry/_runtime.bin

This file was deleted.

Loading