The Mindset
Pillaging is post-exploitation with high privileges. The goal is to extract:
- Credentials — passwords, hashes, keys, tokens
- Sensitive data — PII, internal documents, business data
- Infrastructure intel — internal hostnames, IPs, configs that help you move laterally
- Persistence material — SSH keys, API tokens, service accounts
The difference between enumeration and pillaging is access level. During enumeration you work with what a low-privilege user can see. During pillaging, you have root — every door is open.
Operating System & Environment
Start by confirming full context with elevated access:
Credentials in Configuration Files
Configuration files are the richest source of credentials on any Linux system. Services need to authenticate to databases, APIs, and other services — those credentials live in config files.
Web Application Configs
Database Configuration Files
Service & Application Configs
SSH Keys
SSH keys are the ultimate lateral movement credential — no cracking needed, works immediately.
known_hosts reveals every host this machine has ever SSH’d into. Each entry
is a lateral movement target. Even if the keys are hashed, the IPs/hostnames
are often visible.
Password & Hash Files
Command History Files
Users type passwords directly into terminals constantly. History files capture everything.
Log Files
Logs are a goldmine — applications log errors that often include credentials, and auth logs show activity patterns.
Log locations reference:
Databases
If a database service is running, connect to it directly with root or the credentials you found.
Stored Credentials & Secret Files
Emails & Mail Spools
Internal emails often contain credentials, reset links, and infrastructure information.
Interesting Files Across the System
Memory & Running Process Secrets
Next: System Logs — reading and analyzing logs to understand what happened on a system and find evidence of credentials and activity.