identifying-file-types-and-formats
Identifies a sample''s true file type independent of its extension: matching magic
v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/identifying-file-types-and-formatsWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package06b5ff69…ad0d6b38
06b5ff690dfe…77faad0d6b384 files · 3.3 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/identifying-file-types-and-formats@da7600a
On this page
When to Use
- You receive an unknown sample and must determine what it actually is before choosing tools.
- You suspect masquerading — a
.pdfor.jpgthat is really an executable or script. - You need to detect container formats (ZIP/OLE/ISO) that hide a payload.
Do not use the file extension or the OS-reported type as truth — adversaries rename executables and embed payloads; always confirm by content.
Prerequisites
file/libmagic or an equivalent magic-byte database; the sample handled inertly in the lab.
Safety & Handling
- Never open the sample in its associated application during identification; read raw bytes only.
- Keep the disguised extension in mind — a double extension or RTLO trick can mislead the eye.
Workflow
Step 1: Read the magic bytes
Inspect the leading bytes and known offset signatures (e.g., MZ, \x7fELF, %PDF, PK\x03\x04,
OLE D0 CF 11 E0).
python scripts/analyst.py identify sample.datStep 2: Confirm structure
For container formats, confirm internal structure (ZIP central directory, OLE storage, ISO
CD001 at 0x8001) rather than trusting the header alone.
Step 3: Compare against the claimed extension
Flag mismatches: a .jpg whose content is MZ, or a document that is actually a script. These
are strong masquerading indicators.
Step 4: Route to the right analysis
Use the confirmed type to pick the correct workflow (PE static analysis, document analysis, archive extraction).
Validation
- The detected type is confirmed by both magic bytes and structural checks, not magic alone.
- Extension/content mismatches are explicitly reported.
- The result correctly routes the sample to the appropriate analysis skill.
Pitfalls
- Trusting the first 2 bytes only; some formats need offset or structural confirmation.
- Missing polyglot files that are valid as two formats at once.
- Overlooking nested containers (archive inside archive) that hide the real payload.
References
- See
references/api-reference.mdfor the type identifier. - libmagic and the magic-number reference (linked in frontmatter).
Files in this version
references/11.1 KB
- api-reference.md1.1 KB
scripts/12.6 KB
- analyst.py2.6 KB
- LICENSE340 B
- SKILL.md3.0 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumFile · Executable script shipped with the skillscripts/analyst.py
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v1.0.0 | Nov 13, 2026 | da7600a | 06b5ff69 | Signed | – |
More from meltedinhex
All from this publisher- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
- writing-suricata-and-snort-rulesmeltedinhex/writing-suricata-and-snort-rules3
- writing-sigma-detection-rulesmeltedinhex/writing-sigma-detection-rules3
More in Malware and ransomware analysis
See the category- yara-sigsdariushoule/yara-sigs4
- monitoring-darkweb-sourcesmukul975/monitoring-darkweb-sources3
- deploying-ransomware-canary-filesmukul975/deploying-ransomware-canary-files3
- implementing-honeypot-for-ransomware-detectionmukul975/implementing-honeypot-for-ransomware-detection3
- yaraaeondave/yara3
- testing-ransomware-recovery-proceduresmukul975/testing-ransomware-recovery-procedures3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login