Leaked Secret Detected
PKGuardian detected what appears to be a EVM Private Key (0x) in a recent commit.
| Field |
Value |
| Commit |
fb8d6e8047df0672b87e6f10de9fa2d7b0672d2d |
| File |
cb_monitor_state.json |
| Secret (redacted) |
3a718651302ae28ba3936377ccb85ac70b27343046361cdb5ac5fefa514c8ace |
What to do
- Rotate the key immediately. Even if you remove the commit, it may already be cached by bots.
- Revoke the old key in the corresponding service.
- Consider using a
.gitignore or a secrets manager to prevent future leaks.
- Use
git filter-repo or BFG to scrub the key from history if needed.
This issue was opened automatically by PKGuardian - a public GitHub push secret scanner.
If this is a false positive, feel free to close this issue.
Leaked Secret Detected
PKGuardian detected what appears to be a EVM Private Key (0x) in a recent commit.
fb8d6e8047df0672b87e6f10de9fa2d7b0672d2dcb_monitor_state.json3a718651302ae28ba3936377ccb85ac70b27343046361cdb5ac5fefa514c8aceWhat to do
.gitignoreor a secrets manager to prevent future leaks.git filter-repoor BFG to scrub the key from history if needed.This issue was opened automatically by PKGuardian - a public GitHub push secret scanner.
If this is a false positive, feel free to close this issue.