# π Security & Privacy Guide
**π‘οΈ Comprehensive security measures and incident response**
*Protect your accounts and maintain privacy*
---
## π― Security Overview
This guide explains how the script **detects security-related issues**, what it does automatically, and how you can **resolve incidents** safely.
### **Security Features**
- π¨ **Automated detection** β Recognizes account compromise attempts
- π **Emergency halting** β Stops all automation during incidents
- π **Strong alerts** β Immediate notifications via Discord/NTFY
- π **Recovery guidance** β Step-by-step incident resolution
- π **Privacy protection** β Local-only operation by default
---
## π¨ Security Incidents & Resolutions
### **Recovery Email Mismatch**
#### **Symptoms**
During Microsoft login, the page shows a masked recovery email like `ko*****@hacker.net` that **doesn't match** your expected recovery email pattern.
#### **What the Script Does**
- π **Halts automation** for the current account (leaves page open for manual action)
- π¨ **Sends strong alerts** to all channels and engages global standby
- βΈοΈ **Stops processing** β No further accounts are processed
- π **Repeats reminders** every 5 minutes until intervention
#### **Likely Causes**
- β οΈ **Account takeover** β Recovery email changed by someone else
- π **Recent change** β You changed recovery email but forgot to update config
#### **How to Fix**
1. **π Verify account security** in Microsoft Account settings
2. **π Update config** if you changed recovery email yourself:
```json
{
"email": "your@email.com",
"recoveryEmail": "ko*****@hacker.net"
}
```
3. **π Change password** and review sign-in activity if compromise suspected
4. **π Restart script** to resume normal operation
#### **Prevention**
- β
Keep `recoveryEmail` in `accounts.json` up to date
- β
Use strong unique passwords and MFA
- β
Regular security reviews
---
### **"We Can't Sign You In" (Blocked)**
#### **Symptoms**
Microsoft presents a page titled **"We can't sign you in"** during login attempts.
#### **What the Script Does**
- π **Stops automation** and leaves page open for manual recovery
- π¨ **Sends strong alert** with high priority notifications
- βΈοΈ **Engages global standby** to avoid processing other accounts
#### **Likely Causes**
- β±οΈ **Temporary lock** β Rate limiting or security check from Microsoft
- π« **Account restrictions** β Ban related to unusual activity
- π **Verification required** β SMS code, authenticator, or other challenges
#### **How to Fix**
1. **β
Complete verification** challenges (SMS, authenticator, etc.)
2. **βΈοΈ Pause activity** for 24-48h if blocked repeatedly
3. **π§ Reduce concurrency** and increase delays between actions
4. **π Check proxies** β Ensure consistent IP/country
5. **π Appeal if needed** β Contact Microsoft if ban is suspected
#### **Prevention**
- β
**Respect rate limits** β Use humanization settings
- β
**Avoid patterns** β Don't run too many accounts from same IP
- β
**Geographic consistency** β Use proxies from your actual region
- β
**Human-like timing** β Avoid frequent credential retries
---
## π Privacy & Data Protection
### **Local-First Architecture**
- πΎ **All data local** β Credentials, sessions, logs stored locally only
- π« **No telemetry** β Zero data collection or external reporting
- π **No cloud storage** β Everything remains on your machine
### **Credential Security**
```json
{
"accounts": [
{
"email": "user@example.com",
"password": "secure-password-here",
"totpSecret": "optional-2fa-secret"
}
]
}
```
**Best Practices:**
- π **Strong passwords** β Unique, complex passwords per account
- π **2FA enabled** β Time-based one-time passwords when possible
- π **File permissions** β Restrict access to `accounts.json`
- π **Regular rotation** β Change passwords periodically
### **Session Management**
- πͺ **Persistent cookies** β Stored locally in `sessions/` directory
- π **Encrypted storage** β Session data protected at rest
- β° **Automatic expiry** β Old sessions cleaned up automatically
- ποΈ **Per-account isolation** β No session data mixing
---
## π Network Security
### **Proxy Configuration**
```json
{
"browser": {
"proxy": {
"enabled": true,
"server": "proxy.example.com:8080",
"username": "user",
"password": "pass"
}
}
}
```
**Security Benefits:**
- π **IP masking** β Hide your real IP address
- π **Geographic flexibility** β Appear from different locations
- π **Traffic encryption** β HTTPS proxy connections
- π‘οΈ **Detection avoidance** β Rotate IPs to avoid patterns
### **Traffic Analysis Protection**
- π **HTTPS only** β All Microsoft communications encrypted
- π« **No plaintext passwords** β Credentials protected in transit
- π‘οΈ **Certificate validation** β SSL/TLS verification enabled
- π **Deep packet inspection** resistant
---
## π‘οΈ Anti-Detection Measures
### **Humanization**
```json
{
"humanization": {
"enabled": true,
"actionDelay": { "min": 150, "max": 450 },
"gestureMoveProb": 0.4,
"gestureScrollProb": 0.2
}
}
```
**Natural Behavior Simulation:**
- β±οΈ **Random delays** β Variable timing between actions
- π±οΈ **Mouse movements** β Subtle cursor adjustments
- π **Scrolling gestures** β Natural page interactions
- π² **Randomized patterns** β Avoid predictable automation
### **Browser Fingerprinting**
- π **Real user agents** β Authentic browser identification
- π± **Platform consistency** β Mobile/desktop specific headers
- π§ **Plugin simulation** β Realistic browser capabilities
- π₯οΈ **Screen resolution** β Appropriate viewport dimensions
---
## π Monitoring & Alerting
### **Real-Time Monitoring**
```json
{
"notifications": {
"webhook": {
"enabled": true,
"url": "https://discord.com/api/webhooks/..."
},
"ntfy": {
"enabled": true,
"url": "https://ntfy.sh",
"topic": "rewards-security"
}
}
}
```
**Alert Types:**
- π¨ **Security incidents** β Account compromise attempts
- β οΈ **Login failures** β Authentication issues
- π **Account blocks** β Access restrictions detected
- π **Performance anomalies** β Unusual execution patterns
### **Log Analysis**
- π **Detailed logging** β All actions recorded locally
- π **Error tracking** β Failed operations highlighted
- π **Performance metrics** β Timing and success rates
- π‘οΈ **Security events** β Incident timeline reconstruction
---
## π§ͺ Security Testing
### **Penetration Testing**
```powershell
# Test credential handling
$env:DEBUG_SECURITY=1; npm start
# Test session persistence
$env:DEBUG_SESSIONS=1; npm start
# Test proxy configuration
$env:DEBUG_PROXY=1; npm start
```
### **Vulnerability Assessment**
- π **Regular audits** β Check for security issues
- π¦ **Dependency scanning** β Monitor npm packages
- π **Code review** β Manual security analysis
- π‘οΈ **Threat modeling** β Identify attack vectors
---
## π Security Checklist
### **Initial Setup**
- β
**Strong passwords** for all accounts
- β
**2FA enabled** where possible
- β
**File permissions** restricted to user only
- β
**Proxy configured** if desired
- β
**Notifications set up** for alerts
### **Regular Maintenance**
- β
**Password rotation** every 90 days
- β
**Session cleanup** weekly
- β
**Log review** for anomalies
- β
**Security updates** for dependencies
- β
**Backup verification** of configurations
### **Incident Response**
- β
**Alert investigation** within 15 minutes
- β
**Account verification** when suspicious
- β
**Password changes** if compromise suspected
- β
**Activity review** in Microsoft account settings
- β
**Documentation** of incidents and resolutions
---
## π¨ Emergency Procedures
### **Account Compromise Response**
1. **π Immediate shutdown** β Stop all script activity
2. **π Change passwords** β Update all affected accounts
3. **π Contact Microsoft** β Report unauthorized access
4. **π Audit activity** β Review recent sign-ins and changes
5. **π‘οΈ Enable additional security** β Add 2FA, recovery options
6. **π Document incident** β Record timeline and actions taken
### **Detection Evasion**
1. **βΈοΈ Temporary suspension** β Pause automation for 24-48h
2. **π§ Reduce intensity** β Lower pass counts and frequencies
3. **π Change IPs** β Rotate proxies or VPN endpoints
4. **β° Adjust timing** β Modify scheduling patterns
5. **π Increase humanization** β More natural behavior simulation
---
## π Quick Reference Links
When the script detects a security incident, it opens this guide directly to the relevant section:
- **[Recovery Email Mismatch](#recovery-email-mismatch)** β Email change detection
- **[Account Blocked](#we-cant-sign-you-in-blocked)** β Login restriction handling
---
## π Related Guides
- **[Getting Started](./getting-started.md)** β Initial setup and configuration
- **[Accounts & 2FA](./accounts.md)** β Microsoft account setup
- **[Proxy Configuration](./proxy.md)** β Network privacy and routing
- **[Humanization](./humanization.md)** β Natural behavior patterns