> For the complete documentation index, see [llms.txt](https://docs.getcelsius.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getcelsius.net/troubleshooting/key-not-whitelisted-tamper-warning.md).

# Key Not Whitelisted / Tamper Warning

Authentication, tamper, and whitelist states.

The loader prints `[CELSIUS]` messages for authentication problems. Here's what the common ones mean.

## "Tampering detected"

The script detected its own code was modified. This usually happens with:

* A modified or re-uploaded loader that isn't the official file.
* Copy-pasting from a source that altered the loader.
* Debug tools or other scripts interfering with the protected code.

**Fix:** re-download the official loader from your dashboard or the Discord **Get Script** button and run that. Do not modify the loader.

## "Not whitelisted" / authentication failed

The key hasn't authenticated for this PC. Causes:

* **First run not completed** — run the loader once and enter your serial key so it can bind.
* **Wrong PC** — the key is bound to another machine. See [Resetting Your HWID](/authentication/resetting-your-hwid.md).
* **Key expired or revoked** — check your key status on the dashboard or **Get Stats**.

## False positives

If you get a tamper warning with a completely untouched, freshly downloaded loader, contact support — include which executor and version you're on.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.getcelsius.net/troubleshooting/key-not-whitelisted-tamper-warning.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.