Drive Badger: open source platform for covert data exfiltration operations, ranging from small computers to big servers.

Drive Badger is able to automatically detect and decrypt VeraCrypt-encrypted partitions, but only system partitions. It doesn't support non-system partitions or other VeraCrypt authentication methods: PIN, or keyfiles.

How to provide decryption keys?

See keys-veracrypt-demo repository. It contains a sample veracrypt.keys file.

You can configure multiple such repositories - each such repository should:

  • be cloned to /opt/drivebadger/config/keys-veracrypt-yourchosenname local directory on your Drive Badger persistent partition
  • contain veracrypt.keys file with proper contents (see below)

Local directory doesn't need to contain .git subdirectory, in fact it can be just "floating" directory (created by hand or script, without repository). However if it does, then you can update it automatically using /opt/drivebadger/ (in just 1 step for all repositories).

Do you have more information about these keys?

If you have decryption keys associated (directly or indirectly) with particular drive serial numbers, you can save such keys in keys directory.

If you have any additional useful information about particular keys, allowing you to split them in some way (eg. into cities, buildings, floors, company departments, employee specialties) into smaller groups, you can try:

  • split them into separate repositories
  • configure these repositories across many Drive Badger devices, according to your attack plan

veracrypt.keys file format

veracrypt.keys file can contain:

  • VeraCrypt passwords, one per line
  • comments starting from # sign (without leading spaces)
  • empty lines

Example veracrypt.keys file:

# laptop password

# desktop password

How the keys are matched to encrypted partitions

As opposed to other encryption schemes, VeraCrypt encrypted partitions are not detected by systemd/udevd and not accessible via UUID. Therefore, they are detected in a special way, after processing all partitions that have assigned UUID:

  • each UUID-less partition is checked against the concatenated list of recovery passwords from all veracrypt.keys files
  • when a matching key is found, it's saved in keys directory - so it can be easily reused