atomic-leaked-key-response

Orchestrates atomic Jito-bundle recovery of funds from compromised Solana wallets.

15|2|Updated May 19, 2026
One-click install
npx skills add https://github.com/nirholas/atomic --skill atomic-leaked-key-response-nirholas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: atomic-leaked-key-response
Source: https://github.com/nirholas/atomic/tree/main/skills/leaked-key-response
Command: npx skills add https://github.com/nirholas/atomic --skill atomic-leaked-key-response-nirholas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a Solana wallet private key leaks, sweeper bots typically drain any deposited SOL within 1-3 seconds, making manual recovery nearly impossible. This Skill provides a step-by-step incident-response playbook that sequences atomic Jito-bundle transactions so funds escape the compromised wallet before competing actors can take them. ## Core Features & Use Cases - Triage and Confirmation: Decision tables help determine whether a key is actually leaked (committed .env files, chat pastes, shared hosts) before spending on recovery. - Ordered Recovery Sequence: Orchestrates vault sweeping, SOL consolidation, token rescue per mint, and destination verification in a load-bearing order using Jito bundles. - Edge-Case Handling: Covers Token-2022 transfer hooks, unconfirmed leaks, multiple leaked keys, and pump.fun-seeded destination wallets. - Use Case: A developer accidentally commits a pump.fun creator key to a public GitHub repo. The Skill walks them through sweeping the creator vault, draining residual SOL, rescuing remaining tokens, and verifying the safe destination wallet. ## Quick Start Tell the assistant that your Solana wallet key has leaked and ask it to walk you through the atomic recovery sequence step by step.

Frequently Asked Questions about atomic-leaked-key-response

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I recover funds from a leaked Solana wallet key?▼

Run an ordered sequence of atomic Jito-bundle transactions: first sweep the pump.fun creator vault, then consolidate residual SOL, then rescue each token mint to a safe destination wallet. Each step lands atomically so sweeper bots cannot interleave their own transactions.

What should I do if my private key was committed to GitHub?▼

Treat the key as fully leaked since GitHub history is irreversible and indexers scrape commits in seconds. Immediately set up a clean funder wallet and safe destination, then run the atomic collect and consolidate bundles to drain remaining funds.

Why do sweeper bots drain wallets so fast after a key leak?▼

Sweeper bots continuously monitor for leaked keys and typically drain SOL within 1-3 seconds of any deposit and Token-2022 within 2-4 seconds. This is why recovery must use atomic Jito bundles rather than sequential public transactions.

Can I recover tokens that already left the compromised wallet?▼

No, Solana transactions are irreversible and tokens already transferred out are gone. The recovery sequence only protects funds still held in the leaked wallet, so speed and correct ordering of the sweep steps are critical.

What happens if the Jito bundle fails during recovery?▼

A bundle returning Invalid usually means the tip is too low or the tip-account list drifted; escalate the tip and retry. If the bundle lands but funds remain, a competing collector landed in the same slot and you should re-run immediately.