MetaMask / MetaMask/providers

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

Open
#426 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
268
Forks
130
PR merge metrics
No merged PRs in 30d

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:
  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).

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the referenced commit and src/messages.ts to confirm the exposed MiniMax key, then inspect the repository history for copies of it. Coordinate revocation and replacement, remove the committed secret, update .gitignore, and scrub the history; review MiniMax usage logs as part of verification. Done means the old key is inactive and no longer present in the current tree or Git history.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.