Portable Forensics with Toby: A Raspberry Pi Toolkit

Whether teaching, investigating, or tinkering on the road, there’s an undeniable appeal to a device that’s self-contained, headless, and versatile enough to support forensic analysis, malware triage, and field acquisition. That idea became the seed for Toby — a Raspberry Pi Zero 2 W–based micro-rig that can be managed from an iPad or mobile device.

It started off with a “what could I do with at Raspberry Pi” and the final result: a fully functional, go-anywhere forensics toolkit that fits in the palm of your hand, carefully packed into a Grid-It travel kit and loaded with purpose.


Why Build Toby?

Toby wasn’t born from necessity. It came from a blend of curiosity, constraint, and the spirit of joyful overengineering. The goal wasn’t just to get Kali Linux running on a Pi — that’s been done. The challenge was in how much capability could be packed into a minimalist footprint without compromising on control, security, or style.

Some driving goals from the outset:

  • Headless-first: Must be operable via SSH, or VNC — no screen needed.
  • Kali-based: Full access to familiar forensic and pentest tooling.
  • Discreet and functional: Everything should be secure, practical, and stowable.
  • Modular connectivity: USB OTG, video capture, remote keyboard/mouse, and VPN support all needed to be viable.
  • Portable power: Run from a battery pack for field ops or demo use without dependency on AC power.

Hardware Selection

Raspberry Pi Zero 2 W

The Pi Zero 2 W hits a sweet spot. It has enough power to run full Kali and perform triage analysis, especially with swap and careful headless tuning. It supports USB OTG and can be powered over micro-USB, making it ideal for lightweight builds.

Grid-It Travel Kit: The Physical Layout

Instead of housing the components in a fixed enclosure, I opted for flexibility: a Grid-It organizer sleeve. It allows each cable and tool to remain accessible and secured via elastic straps — perfect for quick swaps or field reconfiguration.

The current loadout includes:

  • Raspberry Pi Zero 2 W 
  • HDMI mini to full adapter (for display recovery if needed)
  • USB micro to USB-C adapter combo (for powering Pi from laptop, iPad, or battery pack)
  • Anker battery pack (portable, long runtime)
  • Wireless keyboard (compact; paired via Bluetooth or USB receiver)
  • USB capture device (used for teaching, demoing webcam/VNC sessions)
  • Short USB OTG cable

The setup is light, self-contained, and TSA-friendly — a true digital go-bag for the forensically inclined.


Portable Power

Toby can be powered from the USB port of an iPad or from a battery pack or AC adapter, making it extremely flexible for field use.

Toby powered from iPad Pro
Toby powered from portable battery

Software

The OS is a clean, headless Kali Linux image configured specifically for ARM on the Pi Zero 2 W. Rather than trying to turn it into a desktop experience (even though it can), it boots fast, runs lean, and drops me directly into a terminal where I can get to work — whether over SSH or local keyboard.

Core Components:

Base image: Raspbian (Debian-based) with Kali tools manually installed

Metapackages:

  • kali-linux-forensic
  • kali-linux-desktop
  • core/default Kali utilities and command-line tools, incrementally layered until the system was functionally equivalent to a full Kali install (minus unnecessary services)

Additional Software Intstalled:

MalChela (CLI) running on Toby
Kali Forensics tools on Toby
MalChela GUI running on Toby

🔍 Toby-find: Your On-Device Forensics Cheat Sheet

One of Toby’s handiest features isn’t a tool you run—it’s a tool to remember tools. toby-find is a simple but powerful command-line helper built into the system. It gives you fast access to a curated list of CLI forensics tools available on Toby, along with short descriptions and usage tips.

It’s like having a searchable cheat sheet, always available—perfect for field use when memory is fuzzy or connectivity is limited.

toby-find utility

What It Does

When you run:

toby-find [keyword] 

it will search the help file for any tool(s) mentioning the keyword in name or description, and provide back a simple command syntax for each tool.

Example:

dwmetz@toby:~$ toby-find strings

Tool:        mstrings
Description: Extracts printable strings from files and maps them to MITRE ATT&CK techniques.
Example:     mstrings suspicious.exe
Category:    Malware
--------------------------------------------------
Tool:        strings_to_yara
Description: Generates a basic YARA rule from strings gathered manually or via mstrings.
Example:     strings_to_yara
Category:    Malware
--------------------------------------------------
Tool:        floss
Description: Extracts obfuscated strings from malware binaries.
Example:     floss suspicious.exe
Category:    Forensics
--------------------------------------------------
Tool:        rephrase
Description: Analyzes and reformats strings from documents or binaries.
Example:     rephrase input.txt
Category:    Forensics
--------------------------------------------------

Installed Tools:

Many of the tools are native to Kali, but some, including MalChela, were compiled manually or added through custom scripts. (Bold == MalChela tools or custom scripts.)

Tool NameDescription
batCat replacement with syntax highlighting and Git integration.
binwalkScans binaries for embedded files and executable code.
bulk_extractorExtracts artifacts like emails and credit card numbers from disk images.
combine_yaraCombines multiple YARA rule files into a single merged rule set.
dffDigital Forensics Framework with CLI and GUI modes.
digPerforms DNS lookups to retrieve domain IPs and records.
exiftoolDisplays metadata from images, PDFs, and other file types.
extract_samplesExtracts files from password-protected ZIP and RAR archives.
fileanalyzerAnalyzes file metadata, headers, and hashes to assist triage and detection.
fileminerRecursively scans a directory for files of interest based on extensions and type.
flossExtracts obfuscated strings from malware binaries.
foremostRecovers deleted files from disk images using file carving.
hashcheckComputes multiple cryptographic hashes and prints them side-by-side.
hashdeepGenerates and verifies file hashes for entire directories.
hashitQuickly generate MD5, SHA1, SHA256, and SHA512 hashes of a file.
htopInteractive system monitor showing real-time process usage.
ipcalcPerforms subnet calculations for IP ranges.
ipstatusShows interface configuration and public IP address.
malchelaMain CLI launcher for the MalChela forensic toolkit, with a menu-driven interface.
malhashLooks up file hashes using VirusTotal and MalwareBazaar.
moshSSH replacement that maintains session state during roaming.
mstringsExtracts printable strings from files and maps them to MITRE ATT&CK techniques.
mzcountTallies file extensions and MIME types in a directory.
mzhashRecursively hash all files in a directory using MD5.
ncduDisk usage analyzer with an interactive interface.
nmapPerforms host discovery and port scanning on a network.
nsrlqueryChecks file hashes against the National Software Reference Library.
p0fPerforms passive OS fingerprinting from live network traffic.
reglookupQueries Windows Registry hives from the command line.
regripperExtracts and parses registry artifacts using Perl-based plugins.
rephraseAnalyzes and reformats strings from documents or binaries.
rifiuti2Parses Windows Recycle Bin INFO2 files for forensic analysis.
rkhunterScans the system for known rootkits and suspicious behavior.
rsakeyfindSearches RAM dumps for RSA private key patterns.
safecopyRecovers data from damaged or unstable storage media.
samdump2Extracts password hashes from Windows SAM files.
scalpelPerforms file carving on disk images using headers/footers.
screenTerminal window manager similar to tmux.
scrounge-ntfsRecovers deleted files from NTFS file systems.
speedPerforms a network speed test from the command line.
sshStandard secure shell for remote command-line access.
ssdeepPerforms context-triggered piecewise hashing (fuzzy hashing).
strings_to_yaraGenerates a basic YARA rule from strings gathered manually or via mstrings.
tcpdumpCaptures and displays raw network packets in real time.
tmuxTerminal multiplexer for managing multiple sessions.
toby-findLists available tools and examples installed on the Toby system.
truecrackAttempts to brute-force passwords for TrueCrypt volumes.
tsharkTerminal version of Wireshark for packet capture and filtering.
undbxExtracts messages from Outlook Express DBX mailboxes.
unarExtracts files from .rar and other archives.
unhideDetects hidden processes and tasks in Linux systems.
upxCompresses or decompresses executable files.
uptimeDisplays system uptime and load averages.
vinettoParses thumbnail caches from Internet Explorer and Firefox.
vnc-offStops the running VNC session.
vnc-onStarts a VNC server session for remote desktop access.
volatility3Memory forensics framework for analyzing RAM dumps.
vpn-offStops the active OpenVPN session.
vpn-onStarts the OpenVPN client using the configured lab connection.
winregfsMounts Windows Registry hives as a read-only virtual filesystem.
xmountConverts between forensic image formats (e.g. EWF to RAW).
xmzhashRecursively hash all files in a directory using MD5, SHA1, and SHA256.

This setup enables lightweight static analysis, file triage, memory inspection, and network capture — all from a Pi that fits in a Altoids case.


Build Process (Step by Step)

1. Flashing and First Boot

Using the Raspberry Pi Imager, I selected the ARM64 Raspbian image, added SSH and Wi-Fi credentials, and flashed the SD card.

Tip: The “advanced” options in Raspberry Pi Imager let you configure headless behavior up front, saving time on first boot.

2. Swap, Networking, and System Setup

The Pi Zero 2 W is modest on RAM — just 512MB — so swap is essential. I configured a persistent 2GB file-based swap at /swapfile, which gave the system enough breathing room to compile, run heavier tools, and avoid out-of-memory crashes during extended sessions.

Networking is Wi-Fi-only, so multiple SSIDs were configured using wpa_supplicant.conf for home and hotspot SSIDs. VPN has also been configured for remote access to my home malware lab.

3. Building and Installing MalChela

I cloned the full MalChela repository directly and compiled tool-by-tool:

cd MalChela
for tool in fileanalyzer mstrings hashcheck extract_samples ...; do
  cargo build --release -p $tool
done

4. Screen Choices

In addition to headless-mode, you can use a typical keyboard/monitor/mouse setup, for either cli mode or full gui.

The Pi Zero 2 W supports HDMI output via its mini-HDMI port, so you can plug it directly into any monitor or TV using a mini-HDMI to HDMI cable or adapter. For true portability, I needed something more flexible that didn’t require me packing a separate screen.

Toby running in desktop mode

To solve this, I added a compact USB-based HDMI capture device to the kit. It effectively turns any mobile device into a live monitor. By connecting Toby’s HDMI out to the capture card and plugging it into my iPad or iPhone,  I can preview the Pi’s screen on the go. This setup also works with OBS, QuickTime, or dedicated capture apps for recording demos or screen sessions — handy for teaching or documenting tool usage.

Input is handled with a small wireless Bluetooth keyboard, which pairs cleanly with Toby for direct control. This combo — Pi output through HDMI capture and keyboard input via Bluetooth — lets me interact with Toby completely untethered.

In practice, I rarely need the GUI. But when I do, this setup lets me bring it up quickly without dragging along a dedicated screen.


Final Result: What Toby Can Do

Toby isn’t just a cute Pi rig with a name. It’s a real tool, and its current feature set reflects that.

💼 Mobile Forensics Platform

  • Mount, triage, and scan USB drives with fileanalyzer
  • Run YARA scans and generate custom rules from strings
  • Look up hashes via VirusTotal, MalwareBazaar, and NSRL
  • Analyze memory dumps with Volatility 3 (including plugin selection)
  • Run offline IOCs scans via mstrings or custom shell scripts

What’s Next for Toby

Building Toby was an exercise in maximizing power in a small footprint through deliberate choices. For educators, students, and curious tinkerers, Toby proves that hands-on, portable, and fun learning and teaching forensics can be achieved. If you’re building your own, start with what you have: a Pi, a Grid-It, and your imagination. Sometimes, the best tools aren’t the ones with the biggest screens or fastest chips—they’re the ones you have with you.

I’m already thinking about upgrades. One in consideration is a case upgrade, a true lunchbox-style metal enclosure — something retro and rugged, with a small screen inside the lid.

Let me know in the comments if you’d like a public release of toby-find as an add-on to install for Kali builds for forensics and malware analysis.

MalChela v3.0: Case Management, FileMiner, and Smarter Triage

With the release of MalChela v3.0, I’m introducing features that shift the focus from tool-by-tool execution to a more structured investigative workflow. While the core philosophy of lightweight, file-first analysis remains unchanged, this version introduces smarter ways to manage investigations, track findings, and automate common analysis patterns, all with minimal fuss.

In this post, I’ll walk through the new Case Management system, the replacement of MismatchMiner with FileMiner, and the ability to identify and launch suggested tools — even in batch — based on file characteristics. These changes aim to reduce friction in multi-tool workflows and help analysts move faster without losing visibility or control.

Cases: A Lightweight Way to Stay Organized

Until now, MalChela has operated in an ephemeral mode. You selected a tool, pointed it at a file or folder, and reviewed the output. Any saved results would be grouped by tool, but without much context.

Cases change that. In v3.0, you can start a new case from a file or folder — and everything from that point forward is grouped under that case. Tool outputs are saved to a dedicated case folder, file hashes are tracked, and metadata is preserved for review or reanalysis.

Case Management

You don’t need to create a case for every run — MalChela still supports standalone tool execution. But when you’re working with a malware sample set, an incident directory, or a disk image extract, cases give you the ability to:

  • Save tool results in a consistent location
  • Track analysis history per file
  • Reopen previous sessions with full context
  • Add notes, tags, and categorization (e.g., “suspicious”, “clean”, “needs review”)

Hello FileMiner: Goodbye MismatchMiner

The MismatchMiner tool was originally designed to surface anomalies between file names and actual content — a common trick in malicious attachments or script dropper chains. It worked well, but its scope was narrow.

FileMiner replaces it, expanding the logic to support full file-type classification and metadata inspection across an entire folder. It still flags mismatches, but now it also:

  • Detects embedded file types using magic bytes
  • Groups files by class (e.g., images, documents, executables, archives)
  • Calculates hashes for correlation and NSRL comparison
  • Extracts size, extension, and other key metadata
  • Saves both a human-readable .txt summary and a structured .json report

The output is designed to be used both manually and programmatically — which brings us to one of v3.0’s most important additions: tool suggestions.

The new FileMiner app

Suggested Tools and Batch Execution

Once FileMiner runs, it doesn’t just stop at reporting. Based on each file’s type and characteristics, it can now suggest one or more appropriate tools from the MalChela suite.  These suggestions are surfaced right in the GUI — or in the CLI if you’re running FileMiner interactively. From there, you can choose to launch the recommended tool(s) on a per-file basis or queue up several for batch execution.

This makes it much faster to pivot from triage to deeper inspection. No more switching tools manually or copying paths. You stay within the flow — and more importantly, you reduce the risk of skipping important analysis steps.

CLI and GUI Improvements Aligned

These features are available in both the CLI and GUI editions of MalChela. In the CLI, FileMiner presents an interactive table of results. You can pick a file, see its suggested tools, and choose which one to run. When you’re done, you can return to the table and continue with the next file.

The GUI extends this even further, allowing you to:

  • View and scroll through full case history
  • Run tools with live output streaming
  • Reopen previous FileMiner runs from saved reports
  • Run all suggested tools on all files with one click (if desired)

These features let you treat MalChela more like a toolbox with memory, not just a launcher.


CLI Enhancements:

The command-line interface has also received a quiet but meaningful upgrade. Tool menus are now organized with clear numeric indexes and shortcodes, making it faster to navigate and launch tools without needing to retype full names. This small change goes a long way during repetitive tasks or when working in a time-constrained triage setting.

FileMiner supports an interactive loop: after running a tool on a selected file, you’re returned to the main results table — no need to restart the scan or re-navigate the menu. This allows you to run additional tools on different files within the same dataset, making FileMiner feel more like a lightweight control center for follow-up actions. It’s a subtle shift, but one that significantly reduces friction in batch-style or exploratory workflows.


Closing Thoughts

MalChela 3.0 reflects a steady evolution — not a revolution. It’s built on real-world feedback and a desire to make forensic and malware analysis a little less scattered. Whether you’re a one-person IR team or just trying to stay organized during a reverse engineering exercise, the new case features and smarter triage capabilities should save you time.

If you’ve been using MalChela already, I think this update will feel like a natural (and welcome) extension. And if you haven’t tried it yet, there’s never been a better time to start.

Download: https://github.com/dwmetz/MalChela/releases

User Guide: https://dwmetz.github.io/MalChela/

Hashes for the Masses: Finding What Matters in a Sea of Samples

A short while back, I released a pair of tools for building MD5 hash sets — one targeting known-good gold builds, the other designed for scanning malware corpora. The goal was simple: generate hash sets that could be used in forensics tools like Axiom Cyber to flag IOC matches during case processing.

Recently, I hit a familiar problem: I had a hash and wanted to know if that file existed in my malware library. Step one was updating my tooling to support SHA256 — the modern standard for hash sharing — and regenerating the hash sets. That part worked. I could search for a hash and confirm whether it appeared in my set.

But what if I got a match?

At that point, I realized: I had no way to correlate the match back to the original file. With ~30,000 samples in the library, “just eyeballing it” wasn’t an option.

As I’ve been coding up new tools — or revisiting earlier ones — I’ve discovered that rabbit holes have rabbit holes.

So I updated the SHA256 tool to not only generate a hash set, but also produce a .tsv lookup table mapping each hash to its full file path. This made the sets usable both in forensics platforms and for custom lookups in more ad hoc workflows. As they say: necessity is the mother of intention.

Of course, that led to another realization. I now had four hashing tools — two for MD5 (MZ and non-MZ), and two for SHA256. The “Hashing Tools” section in MalChela was getting a bit crowded.

Back to the drawing board.


The Result: Three Unified Tools

I consolidated and upgraded everything into three tools — all of which support both CLI and GUI usage.

#️⃣ MZHash (replaces mzmd5)

• Uses YARA to recursively scan for files with an MZ header (i.e., Windows executables and DLLs)

• Generates one hash file per selected algorithm: MD5, SHA1, SHA256

• Also creates a .tsv lookup file for each, mapping hashes to paths

cargo run -p mzhash /directory/to/scan -- -a MD5 -a SHA1 -a SHA256

Via GUI, you can browse to the folder and check boxes for each algorithm.


🌐 XMZHash (replaces xmzmd5)

• Uses YARA to skip over files with MZ, ZIP, or PDF headers

• Hashes everything else — ideal for surfacing Linux, Mac, or unusual samples from a mixed malware corpus

• Also supports .tsv lookup file generation

cargo run -p xmzhash /directory/to/scan -- -a MD5 -a SHA1 -a SHA256

The idea: hash what’s not obviously Windows, document-related, or un-extracted samples.

XMZHash

🔍 HashCheck

Okay, so naming might not be my strong suit. But this tool’s direct.

• Provide a hash value and a .txt or .tsv hash set

• It checks for matches, and if you’re using a .tsv, it shows the file path of the match

• Great for live triage, corpus hunting, or checking known-bads

cargo run -p hashcheck ./hashes.tsv 44d88612fea8a8f36de82e1278abb02f
Hash Check

In Summary

MalChela 2.2.1 expands its hashing toolkit with the introduction of HashCheck, MZHash, and XMZHash — giving analysts faster ways to flag known-good, isolate unknowns, and build actionable sets. In this release, we’ve also said goodbye to legacy tools, standardized output saving, and doubled down on clarity across both CLI and GUI workflows.

Download: https://github.com/dwmetz/MalChela/releases

User Guide: https://dwmetz.github.io/MalChela/

MalChela 2.2 “REMnux” Release

MalChela’s 2.2 update is packed with practical and platform-friendly improvements. It includes native support for REMnux, better tool settings, and deeper integrations with analysis tools like YARA-X, Tshark, Volatility3, and the newly improved fileanalyzer module.

🦀 REMnux Edition: Built-In Support, Zero Tweaks

When the GUI loads a REMnux-specific tools.yaml profile, it enters REMnux mode.

Screenshot of yaml configuration applying REMnux mode

Native binaries and Python scripts like capa, oledump.py, olevba, and FLOSS are loaded into the MalChela tools menu, allowing you to mix and match operations with the embedded MalChela utilities and the full REMnux tool stack. No manual configuration needed—just launch and go. MalChela currently supports the following REMnux programs right out of the box:

Tool Name Description
binwalkFirmware analysis and extraction tool
capaIdentifies capabilities in executable files
radare2Advanced reverse engineering framework
Volatility 3Memory forensics framework for RAM analysis
exiftoolExtracts metadata from images, documents, and more
TSharkTerminal-based network packet analyzer (Wireshark CLI)
mraptorDetects malicious macros in Office documents
oledumpParses OLE files and embedded streams
oleidIdentifies features in OLE files that may indicate threats
olevbaExtracts and analyzes VBA macros from Office files
rtfobjExtracts embedded objects from RTF documents
zipdumpInspects contents of ZIP files, including suspicious payloads
pdf-parserAnalyzes structure and contents of suspicious PDFs
FLOSSReveals obfuscated and decoded strings in binaries
clamscanOn-demand virus scanner using ClamAV engine
stringsExtracts printable strings from binary files
YARA-XNext-generation high-performance YARA rule scanner

If you only need a subset of tools you can easily save and restore that a custom profile.


TShark Panel with Built-In Reference

Tshark and the integrated field reference

A new TShark integration exposes features including:

  • A filter builder panel
  • Commonly used fields reference
  • Tooltip hints for each example (e.g., `ip.addr == 192.168.1.1` shows “Any traffic to or from 192.168.1.1”)
  • One-click copy support

This helps analysts build and understand filters quickly—even if TShark isn’t something they use every day. Using the syntax builder in MalChela you can use the exact commands directly in Tshark or Wireshark.


YARA-X Support (Install Guide Included)

YARA-X module in MalChela

Support for YARA-X (via the `yr` binary) is now built in. YARA-X is not bundled with REMnux by default, but install instructions are included in the User Guide for both macOS and Linux users.

Once installed, MalChela allows for rule-based scanning from the GUI,and with YARA-X, it’s faster than ever.


fileanalyzer: Fuzzy Hashing, PE Metadata, and More

Updated FileAnalyzer Module

MalChela’s fileanalyzer tool has also been updated to include:

  • Fuzzy hashing support via `ssdeep`
  • BLAKE3 hashing for fast, secure fingerprints
  • Expanded PE analysis, including:
  • Import and Export Table parsing (list of imported and exported functions)
  • Compilation Timestamp (for detection of suspicious or forged build times)
  • Section Characteristics (flags like IMAGE_SCN_MEM_EXECUTE, IMAGE_SCN_CNT_CODE, etc., for detecting anomalous sections)

These improvements provide deeper insight into executable structure, helping analysts detect anomalies such as packers, suspicious timestamps, or unexpected imports/exports. Useful for everything from sample triage to correlation, fileanalyzer now digs deeper—without slowing down.


Memory Forensics Gets a Boost: Volatility 3 Now Supported

With the 2.2 release, MalChela introduces support for Volatility 3, the modern Python-based memory forensics framework. Whether you’re running MalChela in REMnux or on a customized macOS or Linux setup, you can now access the full power of Volatility directly from the MalChela GUI.

Volatility 3 in MalChela

There’s an intuitive plugin selector that dynamically adjusts available arguments based on your chosen plugin,. You can search, sort, and browse available plugins, and even toggle output options like –dump-dir with ease.

Like Tshark, there is an added plugin reference panel with searchable descriptions and argument overviews — a real time-saver when navigating Volatility’s deep and often complex toolset.

Volatility Plugin Reference

Smarter Tool Configuration via YAML

The tool configuration system continues to evolve:

  • Tools now declare their input type (file, folder, or hash)
  • The GUI dynamically adjusts the interface to match
  • Alternate profiles (like REMnux setups) can be managed simply by swapping `tools.yaml` files via the GUI
  • Easily backup or restore your custom setups
  • Restore the default toolset to get back to basics

This structure helps keep things clean—whether you’re testing, teaching, or deploying in a lab environment.


Embedded Documentation Access

The GUI now includes a link to the full MalChela User Guide in PDF. You can also access the documentation online.

From tool usage and CLI flags to configuration tips and install steps, it’s all just a click away—especially useful in offline environments or when onboarding new analysts. I’ll be honest, this is likely the most comprehensive user guide I’ve ever written.


Whether you’re reviewing binaries, building hash sets, or exploring network captures—MalChela 2.2 is designed bring together the tools you need, and make it easier to interoperate between them.

The new REMnux mode makes it even easier to get up and running with dozens of third party integrations.

Have an idea for a feature or application you’d like to see supported — reach out to me.


GitHub: REMnux Release

MalChela User Guide: Online, PDF, Web

Shop: T-shirts, hats, stickers, and more