[Security] Your MiniMax API key was committed to this repo

Nobody has claimed this yet.

Hey! Just a heads-up -- I ran a scan and it looks like an API key got committed to this repo, and it's still active.

| Detail | Value |
|--------|-------|
| Provider | MiniMax |
| File | `src/messages.ts` |
| Source | https://github.com/MetaMask/providers/blob/4ac0b3e2df7de682a95d50e3429dadb0995862cf/src/messages.ts |

### What's the risk?

The key is still live -- anyone who comes across it can use it, burning through your credits or quota.

### What to do:

1. **Revoke** the key in your MiniMax dashboard
2. Generate a new key and swap it in
3. Delete the key from the committed file and add `.env` to `.gitignore`
4. Check your MiniMax usage logs for anything suspicious
5. Scrub the key from git history with `git filter-branch` or BFG

Once you've sorted it out, just close this issue.

---

This is a free public-service scan. If it helped, you can buy me a coffee at https://ko-fi.com/cheeseup (no pressure at all).

Start by inspecting the referenced commit and src/messages.ts to verify the exposed MiniMax key, then review the MiniMax dashboard and usage logs. Coordinate key revocation and replacement, remove the key from the file and git history, and update .gitignore as described. Done means the exposed credential is no longer usable or present in repository history.

Written by the indexing model from the issue text.