Overview

MalChela web interface

MalChela Web Interface

MalChela CLI

MalChela CLI

MalChela Core Tools

These built-in programs provide fast, flexible functionality for forensics and malware triage.

Program Function
Combine YARAPoint it at a directory of YARA files and it will output one combined rule
Extract SamplesPoint it at a directory of password protected malware files to extract all
File AnalyzerGet the hash, entropy, packing, PE info, YARA and VT match status for a file
File MinerScans a folder for file type mismatches and metadata, and provides suggested tools
Hash CheckCheck a hash against a .txt or .tsv lookup table
Hash ItPoint it to a file and get the MD5, SHA1 and SHA256 hash
mStringsAnalyzes files with Sigma rules (YAML), extracts strings, matches ReGex
MZHashRecurse a directory, for files with MZ header, create hash list and lookup table
MZcountRecurse a directory, uses YARA to count MZ, Zip, PDF, other
NSRL QueryQuery a MD5 or SHA1 hash against NSRL
Strings to YARAPrompts for metadata and strings (text file) to create a YARA rule
Threat Intel QueryMulti-source hash and URL lookup. Hash: VT, MB, OTX, HA, FileScan, Malshare, MetaDefender, ObjectiveSee. URL: VT, urlscan.io, Google Safe Browsing. Web interface supports file-to-hash and QR code decode.*
XMZHashRecurse a directory, for files without MZ, Zip or PDF header, create hash list and lookup table

Mac Analysis Tools

Dedicated tools for static analysis of macOS binaries, bundles, and property lists.

Program Function
Code Sign CheckInspects macOS code signing: Developer-signed vs. ad-hoc vs. unsigned, Team ID, Bundle ID, entitlements, and get-task-allow flag
Mach-O InfoParses Mach-O binaries: architecture, linked libraries, section entropy, symbol status, RPATH entries, and deprecated crypto library detection
Plist AnalyzerParses .plist files and .app bundle Info.plist for malware indicators: hidden background agent, ATS disabled, custom URL schemes, env injection

*Threat Intel Query supports optional API keys for its sources. Keys can be managed via the API Keys panel in the MalChela web interface or by placing them in the api/ directory. Sources without configured keys are skipped automatically.