# File Triage

Drop any file. It names the format from its first bytes, hashes it, and opens the parser that reads it: PE, ELF, Mach-O, Office, PDF, plist, or entropy and strings.

Start here when someone hands you a file and asks what it is. Drop it in, and the page reads its first bytes, names the format, hashes it, and opens the parser that understands it. The file never leaves this page.

## How to read it

Read the card first. It says what the file looks like and why the page decided that, so a renamed file cannot fool you. An invoice.pdf that starts with MZ is a Windows executable.

Copy the SHA-256 before anything else. It is the value you search on, share with colleagues, and put in the report.

Then read the format tab. Imports, sections, macros, PDF actions and so forth are where intent shows up. Entropy above about 7.2 bits per byte across most of a file usually means it is packed, compressed or encrypted.

## Tab by tab

### Windows PE

Open it: https://www.cyberkit.win/tools/file-triage/?tab=pe

Static first look at a Windows executable before anyone detonates it. You get the headers, the section table, every import, the exports and the imphash, parsed by hand in the page.

The COFF timestamp is set by the linker and is trivially forged. Treat it as a claim.

Watch the section flags. A section that is both writable and executable, or a raw size of zero with a large virtual size, points at a packer.

The import table is the fastest route to a hypothesis. VirtualAlloc, WriteProcessMemory and CreateRemoteThread together read like injection. Copy the imphash to pivot to related samples.

### ELF and Mach-O

Open it: https://www.cyberkit.win/tools/file-triage/?tab=elf-macho

Read how a Linux or macOS binary was built without running it. The file never leaves the page. You see the header, the sections, the libraries it links and the toolchain quirks that set an intruder's build apart from the distribution's.

Drop an ELF or Mach-O file, or load the sample. Both formats state their own word size and byte order up front, and the parser reads those instead of guessing.

Findings are statements about the toolchain, not verdicts. A stripped, statically linked binary with no build ID in /tmp is worth your time. The same flags on a vendor binary in /usr/bin usually are not.

Linked libraries name capability, not behavior. libcurl means it can talk to the network. It does not say it does, or to where.

### Office (OLE)

Open it: https://www.cyberkit.win/tools/file-triage/?tab=office

Walk a legacy Office document, an Outlook .msg or an MSI as the little filesystem it is. You see every storage and stream with its path and size, and which of them mean macros or embedded objects.

A VBA storage or a Macros stream means a macro project is present. This tool does not decompress VBA, so it tells you where the code lives, not what it does.

ObjectPool and Ole10Native streams carry embedded files. Those are where droppers hide.

A .docx or .xlsm is a ZIP, not a compound file. If this refuses your file, that is usually why.

### PDF

Open it: https://www.cyberkit.win/tools/file-triage/?tab=pdf

Find the parts of a PDF that do things, not the parts that draw pages. Nothing is decompressed or run, so opening a suspect document here is safe in a way that opening it in a reader is not.

/JavaScript means script exists. /OpenAction or /AA pointing at it means it runs without a click. Those are different findings, and only the second is urgent.

More than one %%EOF means the file was saved incrementally. Later revisions can replace earlier objects, so read the last one.

Objects inside an object stream are counted, not read. The coverage note says how many the scan could not see.

### Property list

Open it: https://www.cyberkit.win/tools/file-triage/?tab=plist

Read a macOS property list in either encoding. LaunchAgents and LaunchDaemons are the main macOS persistence mechanism, and they switch between XML and binary freely.

Read ProgramArguments first. That is what actually runs.

RunAtLoad, KeepAlive and StartInterval decide when it runs. A binary under /Users/Shared, /tmp or a hidden folder with any of them set deserves your attention.

The Label is chosen by whoever wrote the file and often imitates com.apple. Dates are counted from 2001-01-01, and this tool shows them in UTC.

### Entropy and strings

Open it: https://www.cyberkit.win/tools/file-triage/?tab=entropy

Two quick reads on any blob. Entropy tells you whether anything in it is readable, and strings tells you what it says. On a packed sample the first says no and the second comes back nearly empty, and that agreement is the finding.

Entropy runs from 0 to 8 bits per byte. Plain text sits around 4 to 5, code around 5 to 6.5, and compressed or encrypted data above 7.5.

High entropy is not a verdict. A ZIP, a JPEG and a signed installer sit in the same band as a packed dropper. Use the window table to find where in the file it climbs.

Strings come in ASCII and UTF-16LE. Windows binaries keep most of their paths and registry keys in UTF-16, so leave both on.

## Related

- [File Hashes](https://www.cyberkit.win/reference/file-hashes/)
- [Decoder: Hash](https://www.cyberkit.win/tools/decoder/?tab=hash)
- [Rule Range: YARA](https://www.cyberkit.win/drills/rule-range/?stage=yara)

Canonical: https://www.cyberkit.win/tools/file-triage/

This runs in the browser. Nothing you enter is uploaded.
