[Security] Your MiniMax API key was committed to this repo
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- security
Research direction
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.
Description
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:
- Revoke the key in your MiniMax dashboard
- Generate a new key and swap it in
- Delete the key from the committed file and add
.envto.gitignore - Check your MiniMax usage logs for anything suspicious
- Scrub the key from git history with
git filter-branchor 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).
- Dominant language
- TypeScript
- Stars
- 268
- Forks
- 130
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MetaMask/providers
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 1/5 Under an hour Newbie friendliness 58/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in MetaMask/providers
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·