A high-performance credential stuffing framework for security professionals.
Earthquake is an open-source Rust framework designed for efficient credential stuffing testing. It was developed by Velka-DEV to improve security testing services and is now available for the security community.
- High Performance: Multi-threaded architecture with configurable thread count for maximum efficiency
- Combo Management: Parse username:password combinations with configurable separators and regex filtering
- Proxy Support: Optional HTTP/SOCKS4/SOCKS5 proxy integration with file or URL sources
- State Control: Pause, resume, and stop operations with automatic progress tracking
- Statistics: Real-time metrics including CPM (checks per minute), hit rate, ETA, etc.
- Retry System: Ensures no lines are skipped due to network errors
- Organized Results: Saves results to categorized files by result type
- Configuration: Save/load configurations for quick startup
- Capture System: Metadata collection for additional information
# Clone the repository
git clone https://github.com/pentech/earthquake.git
cd earthquake
# Build the project
cargo build --releaseHere's a minimal example of using the framework:
use earthquake::{
builder::CheckerBuilder,
checker::CheckModule,
combo::Combo,
proxy::Proxy,
result::CheckResult,
};
use reqwest::Client;
use std::sync::Arc;
struct MyModule;
#[async_trait::async_trait]
impl CheckModule for MyModule {
fn name(&self) -> &str { "my_module" }
fn version(&self) -> &str { "0.1.0" }
fn author(&self) -> &str { "Your Name" }
fn description(&self) -> &str { "My credential checker" }
async fn check(&self, client: Arc<Client>, combo: Combo, proxy: Option<Proxy>) -> CheckResult {
// Your check logic here
// Example: Make a request to validate login credentials
// Return appropriate result
CheckResult::hit().with_message("Login successful")
}
}
#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
// Create and configure checker
let checker = CheckerBuilder::new("my_module")
.with_threads(100)
.with_combo_file("combos.txt")?
.with_proxy_file("proxies.txt")?
.with_check_module(Arc::new(MyModule))
.build()?;
// Start the checker
checker.start().await?;
// Wait until finished or handle pause/resume/stop
Ok(())
}src/builder.rs- Builder pattern for checker configurationsrc/checker.rs- Core checker implementationsrc/combo.rs- Combo parsing and provider implementationssrc/config.rs- Configuration managementsrc/error.rs- Error handlingsrc/proxy.rs- Proxy managementsrc/result.rs- Result type definitionssrc/stats.rs- Statistics trackingsrc/util.rs- Utility functions
Earthquake provides a powerful validation system for filtering combos based on specific rules. This is useful for modules that only work with certain types of credentials.
EmailUsernameValidator: Ensures the username is a valid email addressPasswordLengthValidator: Validates password length within a specified rangeRegexValidator: Validates credentials against a custom regex patternCombinedValidator: Combines multiple validators with AND/OR logic
// Using the factory methods
let validators = vec![
Validators::email(), // Require email format
Validators::password_length(8, 20), // Password between 8-20 chars
];
// Using the builder pattern with a file combo provider
let provider = FileComboProvider::new("combos.txt")
.with_email_validator()
.with_password_length(8, 20)
.with_regex_filter("@gmail\\.com")?;You can implement your own validators by implementing the ComboValidator trait:
struct CustomDomainValidator {
domains: Vec<String>,
}
impl ComboValidator for CustomDomainValidator {
fn validate(&self, combo: &Combo) -> bool {
// Check if username ends with any of the allowed domains
for domain in &self.domains {
if combo.username.ends_with(domain) {
return true;
}
}
false
}
}
// Usage
let validator = Box::new(CustomDomainValidator {
domains: vec!["@gmail.com".to_string(), "@outlook.com".to_string()],
});This tool is intended for security testing with proper authorization only. Unauthorized credential stuffing is illegal and unethical. Always obtain proper permission before conducting security tests.
This project is licensed under the GPLv3 License - see the LICENSE file for details.
Contributions are welcome! Please feel free to submit a Pull Request.