Overview
Jitter strategies introduce controlled randomness into beacon check-in intervals to prevent detection systems from identifying predictable communication patterns. The framework implements two jitter algorithms with configurable variance levels.Why Jitter Matters
Network monitoring systems often detect C2 beacons by identifying fixed-interval traffic patterns:Jitter is applied per beacon interval, not as a one-time offset. Each check-in calculates a new randomized sleep duration.
Jitter Strategies
The framework provides two probability distributions for sleep interval randomization:1. Uniform Jitter
Algorithm: Flat random distribution within ±jitter_pct of base interval- Equal probability for any value within the range
- Simple, predictable variance bounds
- Suitable for most operational scenarios
2. Gaussian Jitter
Algorithm: Bell-curve distribution centered on base interval- Most values cluster near base interval
- Occasional outliers create realistic variance
- Mimics human behavior patterns better
- Recommended for high-security environments
Sleep Floor Constraint
All jitter strategies enforce a minimum sleep duration:Strategy Selection
Choose based on your operational profile:- Uniform - General Use
- Gaussian - High Security
Best for:
- Standard operations
- Predictable variance bounds needed
- Lower to medium evasion profiles
baseline(0% jitter)low(10% jitter)medium(20% jitter)
Implementation Details
Strategy Resolution
The framework resolves strategy names to callable functions:Usage in Beacon Loop
Jitter Percentage Guidelines
0% - No Jitter
Effect: Fixed interval (base_s)Use Case: Testing onlyDetection Risk: ⚠️ High
10% - Light Jitter
Effect: ±3s variance (30s base)Use Case: Low-risk networksDetection Risk: ⚠️ Medium
20% - Moderate Jitter
Effect: ±6s variance (30s base)Use Case: Standard operationsDetection Risk: ⚠️ Low-Medium
40% - Aggressive Jitter
Effect: ±12s variance (30s base)Use Case: High-security environmentsDetection Risk: ✓ Low
Statistical Analysis
Variance Testing
The implementation includes statistical validation:Range Verification
Uniform jitter enforces strict bounds:Operational Considerations
Combining with Other Evasion
Jitter works best when combined with:- Traffic Padding: Obscures message size patterns
- Header Randomization: Prevents User-Agent fingerprinting
- Domain Fronting: Routes traffic through legitimate CDNs
Performance Impact
- CPU: Negligible (simple random number generation)
- Memory: None (stateless calculation)
- Network: Indirect (longer intervals = fewer requests)
Example Configurations
Related Topics
Traffic Profiles
Configure jitter in profile YAML
Traffic Padding
Combine with size obfuscation
Evasion Overview
Complete evasion architecture