Skip to content

ZeroTrace Mobile

Files & settings

Browse the device's storage over Bluetooth, shape its HID profile and identity, spoof its USB descriptors, and back up its config.

The Files and Settings tabs let you manage the connected HID device's storage and shape how it looks and behaves, all over Bluetooth.

Files

The Files browser gives you the device's storage over Bluetooth with no cable in sight.

  • Browse nested folders with breadcrumbs, search, and sort.
  • Transfer: download and upload files (chunked under the hood so even larger files move reliably across a BLE link), and create, delete, and move files.
  • Multi-select to act on a whole batch at once.

This is also where the scripts your Executor runs from the device live.

Settings

Settings is where you shape how the device looks and behaves.

Identity

SettingWhat it controls
Device nameThe name shown for the device.
Advertise nameThe Bluetooth advertising name the device broadcasts.
LED colourThe device's status LED colour.
Power modeThe device's power profile.

HID profile

The full keystroke-injection profile:

  • Keyboard layout, chosen from the supported layout list, so output matches the target without editing payloads. See the ZeroTrace HID reference for the full list of layouts.
  • Auto-disable Caps Lock for predictable output.
  • OS detection on boot.
  • Wipe-after-run.
  • Stealth behaviour.

Backup

You can export the entire configuration and your scripts to a single backup file, and restore from one later, so a device is easy to clone or recover.

USB identity

Because the device presents itself over USB to the target, you control that identity in detail:

Spoof modeWhat it sets
NoneNo spoofing.
Vendor IDJust the vendor ID.
Vendor + product IDVendor and product ID.
FullFull identity, name and serial.

Editable fields: vendor name, product name, serial number, and the raw VID and PID. This lets the hardware appear as whatever class of device a particular test calls for, rather than a generic stick.

Guarded actions

The destructive operations are deliberately gated so a fat-finger never wipes a device by accident:

  • Reboot, format storage, and self-destruct are each behind a typed-confirmation prompt.
  • Even removing a device from the app is forgiving: it is a non-destructive forget that leaves the license on the firmware, with a five-second undo. See Pairing → Removing a device.
Typed confirmation required

Reboot, format, and self-destruct each require you to type a confirmation before they run. There is no single-tap path to a destructive action.