bash history + env harvesting

cat ~/.bash_history ~/.zsh_history /home/*/.bash_history 2>/dev/null ; env

Reads all users' shell histories and the current process environment variables: passwords typed in commands, exported tokens, database credentials, and API keys live in both places more often than it seems.

When you want credentials without touching memory or config files: bash history stores full commands ('mysql -u root -pP@ssw0rd', 'curl -H Authorization: Bearer...') and the process env can have cloud tokens, API keys, or app passwords. It's silent, instant, and works the same on Linux and macOS.

If histories are disabled (HISTSIZE=0 or redirected to /dev/null) or the user uses shells without persistent history, there's nothing to read. Also don't use it if the current process has no interesting variables and you already have a more direct credential path: env regenerates with each process, it's not exhaustive.