[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71ENF2JED781M7DJ1DZXR3W":3,"skill-same:01M71ENF2JED781M7DJ1DZXR3W":89},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":14,"repositoryHtmlUrl":65,"repositoryHomepageUrl":6,"ownerHtmlUrl":66,"ownerBlogUrl":6,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M71ENF2JED781M7DJ1DZXR3W","hardware-firmware-binwalk-detect",null,"Performs firmware image extraction and analysis using binwalk to identify embedded filesystems, compressed archives, bootloaders, kernel images, and cryptographic material. Covers entropy analysis for detecting encrypted or compressed regions, recursive extraction of nested archives, SquashFS\u002FCramFS\u002FJFFS2 filesystem mounting, and string analysis for credential and configuration discovery. Activates for requests involving firmware reverse engineering, IoT device analysis, embedded system security assessment, or router\u002Fcamera firmware extraction.","DCx7C5\u002Fai-marketplace","DCx7C5","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42419559?v=4","01M71C01G2AZV3NTNGWAWSHJPP","DC","01M71C01GQW6G50S2BYMS7PP3E",0,"MIT","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Flinux\u002Fhardware\u002Ffirmware\u002Fbinwalk\u002Fdetect\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"hardware firmware binwalk detect","firmware","detect","binwalk","hardware firmware","hardware","router","detecting","encrypted","de","images","security assessment","image","Bash","firmware-analysis","analysis","entropy","reverse-engineering","assessment","cybersecurity","2026-11-10 10:12:30",false,"---\nname: hardware-firmware-binwalk-detect\ndescription: Performs firmware image extraction and analysis using binwalk to identify embedded filesystems, compressed archives, bootloaders, kernel images, and cryptographic material. Covers entropy analysis for detecting encrypted or compressed regions, recursive extraction of nested archives, SquashFS\u002FCramFS\u002FJFFS2 filesystem mounting, and string analysis for credential and configuration discovery. Activates for requests involving firmware reverse engineering, IoT device analysis, embedded system security assessment, or router\u002Fcamera firmware extraction.\ndomain: cybersecurity\nsubdomain: firmware-analysis\ntags:\n- firmware\n- binwalk\n- extraction\n- entropy\n- IoT-security\n- reverse-engineering\nnist_csf:\n- ID.RA-01\n- PR.PS-01\n- DE.AE-02\nmodel: sonnet\nmaxTurns: 20\ntools: [Read, Bash, Glob, Grep]\ncve:\n- CVE-2021-42373\n- CVE-2021-42374\n- CVE-2016-3116\ncapec: []\n---\n\n# Performing Firmware Extraction with Binwalk\n\n## When to Use\n\n- Analyzing IoT device firmware downloaded from vendor sites or extracted from flash chips\n- Reverse engineering router, camera, or embedded device firmware for vulnerability research\n- Identifying embedded filesystems (SquashFS, CramFS, JFFS2, UBIFS) within firmware blobs\n- Detecting encrypted or compressed regions using entropy analysis\n- Extracting hardcoded credentials, API keys, certificates, or configuration files from firmware\n- Performing security assessments of embedded devices in authorized penetration tests\n\n**Do not use** for analyzing standard desktop application binaries or malware samples that are not firmware images; use dedicated malware analysis tools instead.\n\n## Prerequisites\n\n- binwalk v3.x installed (`pip install binwalk3` or from system package manager)\n- Python 3.8+ with standard libraries (struct, math, hashlib, subprocess)\n- SquashFS tools (`unsquashfs`) for mounting extracted SquashFS filesystems\n- Jefferson for JFFS2 filesystem extraction (`pip install jefferson`)\n- Sasquatch for non-standard SquashFS variants used by vendors like TP-Link and D-Link\n- `strings` utility (GNU binutils) for string extraction\n- Optional: firmware-mod-kit for repacking modified firmware images\n\n## Workflow\n\n### Step 1: Initial Firmware Reconnaissance\n\nPerform a signature scan to identify embedded file types and their offsets:\n\n```bash\n# Basic signature scan - identify all recognized file types\nbinwalk firmware.bin\n\n# Scan with verbose output showing confidence levels\nbinwalk -v firmware.bin\n\n# Scan for specific file types only\nbinwalk -y \"squashfs\" firmware.bin\nbinwalk -y \"gzip\\|lzma\\|xz\" firmware.bin\n\n# Opcode scan to identify CPU architecture\nbinwalk -A firmware.bin\n\n# Scan for raw strings to find version info, URLs, credentials\nbinwalk -R \"password\" firmware.bin\nbinwalk -R \"http:\u002F\u002F\" firmware.bin\n```\n\n### Step 2: Entropy Analysis\n\nAnalyze entropy to identify encrypted, compressed, and plaintext regions:\n\n```bash\n# Generate entropy plot\nbinwalk -E firmware.bin\n\n# Entropy with specific block size for higher resolution\nbinwalk -E -K 256 firmware.bin\n\n# Combined entropy and signature scan\nbinwalk -BE firmware.bin\n```\n\nInterpreting entropy values:\n- **0.0 - 1.0**: Empty or padding regions (null bytes, 0xFF fill)\n- **1.0 - 5.0**: Plaintext data, code, ASCII strings, configuration\n- **5.0 - 7.0**: Compressed data (gzip, LZMA, zlib)\n- **7.0 - 7.99**: Strongly compressed or encrypted data\n- **~8.0**: Maximum entropy, likely encrypted or random data\n\n### Step 3: Extract Embedded Files\n\nExtract all identified components from the firmware image:\n\n```bash\n# Automatic extraction of known file types\nbinwalk -e firmware.bin\n\n# Recursive extraction (matryoshka mode) for nested archives\nbinwalk -Me firmware.bin\n\n# Recursive extraction with depth limit\nbinwalk -Me -d 5 firmware.bin\n\n# Extract specific file type with custom handler\nbinwalk -D \"squashfs filesystem:squashfs:unsquashfs %e\" firmware.bin\n\n# Manual extraction of data at a known offset\ndd if=firmware.bin of=extracted.squashfs bs=1 skip=327680 count=4194304\n```\n\n### Step 4: Mount and Inspect Extracted Filesystems\n\nMount extracted filesystems for deep inspection:\n\n```bash\n# Mount SquashFS filesystem\nmkdir \u002Ftmp\u002Fsquashfs_root\nunsquashfs -d \u002Ftmp\u002Fsquashfs_root extracted.squashfs\n\n# Mount CramFS filesystem\nmkdir \u002Ftmp\u002Fcramfs_root\nmount -t cramfs -o loop extracted.cramfs \u002Ftmp\u002Fcramfs_root\n\n# Extract JFFS2 filesystem\njefferson extracted.jffs2 -d \u002Ftmp\u002Fjffs2_root\n\n# Inspect the extracted filesystem\nls -la \u002Ftmp\u002Fsquashfs_root\u002F\nfind \u002Ftmp\u002Fsquashfs_root -name \"*.conf\" -o -name \"*.cfg\" -o -name \"*.key\"\nfind \u002Ftmp\u002Fsquashfs_root -name \"passwd\" -o -name \"shadow\"\n```\n\n### Step 5: String Analysis and Credential Discovery\n\nSearch extracted filesystem and raw firmware for sensitive data:\n\n```bash\n# Extract all printable strings\nstrings -a firmware.bin > all_strings.txt\nstrings -n 12 firmware.bin | sort -u > long_strings.txt\n\n# Search for credentials and secrets\ngrep -rni \"password\\|passwd\\|secret\\|api_key\\|token\" \u002Ftmp\u002Fsquashfs_root\u002Fetc\u002F\ngrep -rni \"BEGIN.*PRIVATE KEY\" \u002Ftmp\u002Fsquashfs_root\u002F\n\n# Find hardcoded URLs and endpoints\ngrep -rnoE \"https?:\u002F\u002F[a-zA-Z0-9.\u002F?=_-]+\" \u002Ftmp\u002Fsquashfs_root\u002F\n\n# Search for certificate files\nfind \u002Ftmp\u002Fsquashfs_root -name \"*.pem\" -o -name \"*.crt\" -o -name \"*.key\" -o -name \"*.p12\"\n\n# Identify busybox and service versions\nstrings \u002Ftmp\u002Fsquashfs_root\u002Fbin\u002Fbusybox | grep \"BusyBox v\"\ncat \u002Ftmp\u002Fsquashfs_root\u002Fetc\u002Fbanner 2>\u002Fdev\u002Fnull\n```\n\n### Step 6: Generate Firmware Analysis Report\n\nCompile comprehensive extraction and analysis findings:\n\n```\nReport should include:\n- Firmware metadata (vendor, model, version, build date)\n- Identified components with offsets and sizes (bootloader, kernel, filesystem, config)\n- Entropy analysis summary with regions of interest\n- Extracted filesystem structure and key contents\n- Discovered credentials, keys, certificates\n- Identified services, daemons, and their versions\n- Known CVEs applicable to identified component versions\n- Recommendations for hardening or vulnerability remediation\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **Firmware** | Software embedded in hardware devices providing low-level control; typically contains a bootloader, kernel, root filesystem, and configuration data |\n| **Entropy Analysis** | Statistical measurement of randomness in binary data; high entropy indicates encryption or compression, low entropy indicates plaintext or structured data |\n| **SquashFS** | Read-only compressed filesystem commonly used in embedded Linux devices; supports LZMA, gzip, LZO, and zstd compression |\n| **Magic Bytes** | Known byte sequences at fixed offsets that identify file types; binwalk uses a database of magic signatures to detect embedded files |\n| **Matryoshka Extraction** | Recursive extraction mode where binwalk re-scans extracted files for additional embedded content, handling deeply nested archives |\n| **CramFS** | Compressed ROM filesystem designed for embedded systems with limited flash storage; supports only zlib compression |\n| **JFFS2** | Journalling Flash File System version 2, designed for NOR and NAND flash memory in embedded devices |\n\n## Tools & Systems\n\n- **binwalk**: Primary firmware analysis tool for signature scanning, entropy analysis, and automated extraction of embedded files\n- **unsquashfs**: SquashFS extraction utility for mounting read-only compressed filesystems found in router and IoT firmware\n- **jefferson**: Python tool for extracting JFFS2 flash filesystem images commonly found in embedded devices\n- **sasquatch**: Patched SquashFS utility supporting non-standard vendor-modified SquashFS variants\n- **firmware-mod-kit**: Toolkit for extracting, modifying, and repacking firmware images for security testing\n\n## Common Scenarios\n\n### Scenario: Extracting and Auditing Router Firmware for Hardcoded Credentials\n\n**Context**: A security researcher is performing an authorized assessment of a consumer router. The firmware update file was downloaded from the vendor's support page. The goal is to identify hardcoded credentials, insecure default configurations, and known vulnerable components.\n\n**Approach**:\n1. Run `binwalk -e firmware.bin` to perform initial extraction\n2. Use `binwalk -E firmware.bin` to check entropy and identify encrypted regions\n3. Locate the SquashFS root filesystem in the extracted output\n4. Mount with `unsquashfs` and inspect `\u002Fetc\u002Fpasswd`, `\u002Fetc\u002Fshadow`, and web server configs\n5. Search for hardcoded credentials with `grep -rni \"password\" \u002Ftmp\u002Froot\u002Fetc\u002F`\n6. Identify service versions and cross-reference with CVE databases\n7. Check for debug interfaces (telnet, UART, JTAG references) in startup scripts\n8. Examine web application code for authentication bypass or command injection\n\n**Pitfalls**:\n- Some vendors use non-standard SquashFS with custom compression; use sasquatch instead of unsquashfs\n- Encrypted firmware requires decryption keys often found in bootloader or previous unencrypted versions\n- Firmware headers may need to be stripped before binwalk can identify the embedded filesystem\n- Obfuscated strings may evade simple grep searches; use entropy analysis to locate data blobs\n\n## Output Format\n\n```\nFIRMWARE EXTRACTION REPORT\n====================================\nFirmware:         TP-Link TL-WR841N v14\nFile:             wr841nv14_en_3_16_9_up.bin\nSize:             3,932,160 bytes (3.75 MB)\nSHA-256:          a1b2c3d4e5f6...\n\nSIGNATURE SCAN RESULTS\nOffset       Type                          Size\n------       ----                          ----\n0x00000000   U-Boot bootloader header      64 bytes\n0x00020000   LZMA compressed data          1,048,576 bytes\n0x00120000   SquashFS filesystem v4.0      2,752,512 bytes\n0x003B0000   Configuration partition       131,072 bytes\n\nENTROPY ANALYSIS\nRegion 0x000000-0x020000: 4.21 (bootloader - plaintext code)\nRegion 0x020000-0x120000: 7.89 (kernel - LZMA compressed)\nRegion 0x120000-0x3B0000: 7.45 (filesystem - SquashFS compressed)\nRegion 0x3B0000-0x3C0000: 1.12 (config - mostly empty)\n\nEXTRACTED FILESYSTEM\nRoot filesystem: SquashFS v4.0, LZMA compression\nTotal files: 847\nTotal dirs: 112\nBusyBox version: 1.19.4\n\nSECURITY FINDINGS\n[CRITICAL] Hardcoded root password in \u002Fetc\u002Fshadow (hash: $1$...)\n[HIGH]     Telnet daemon enabled by default in \u002Fetc\u002Finit.d\u002FrcS\n[HIGH]     Private RSA key at \u002Fetc\u002Fssl\u002Fprivate\u002Fserver.key\n[MEDIUM]   BusyBox 1.19.4 (CVE-2021-42373, CVE-2021-42374)\n[MEDIUM]   Dropbear SSH 2014.63 (CVE-2016-3116)\n[LOW]      UPnP service enabled by default\n```\n","# Performing Firmware Extraction with Binwalk\n\n## When to Use\n\n- Analyzing IoT device firmware downloaded from vendor sites or extracted from flash chips\n- Reverse engineering router, camera, or embedded device firmware for vulnerability research\n- Identifying embedded filesystems (SquashFS, CramFS, JFFS2, UBIFS) within firmware blobs\n- Detecting encrypted or compressed regions using entropy analysis\n- Extracting hardcoded credentials, API keys, certificates, or configuration files from firmware\n- Performing security assessments of embedded devices in authorized penetration tests\n\n**Do not use** for analyzing standard desktop application binaries or malware samples that are not firmware images; use dedicated malware analysis tools instead.\n\n## Prerequisites\n\n- binwalk v3.x installed (`pip install binwalk3` or from system package manager)\n- Python 3.8+ with standard libraries (struct, math, hashlib, subprocess)\n- SquashFS tools (`unsquashfs`) for mounting extracted SquashFS filesystems\n- Jefferson for JFFS2 filesystem extraction (`pip install jefferson`)\n- Sasquatch for non-standard SquashFS variants used by vendors like TP-Link and D-Link\n- `strings` utility (GNU binutils) for string extraction\n- Optional: firmware-mod-kit for repacking modified firmware images\n\n## Workflow\n\n### Step 1: Initial Firmware Reconnaissance\n\nPerform a signature scan to identify embedded file types and their offsets:\n\n```bash\n# Basic signature scan - identify all recognized file types\nbinwalk firmware.bin\n\n# Scan with verbose output showing confidence levels\nbinwalk -v firmware.bin\n\n# Scan for specific file types only\nbinwalk -y \"squashfs\" firmware.bin\nbinwalk -y \"gzip\\|lzma\\|xz\" firmware.bin\n\n# Opcode scan to identify CPU architecture\nbinwalk -A firmware.bin\n\n# Scan for raw strings to find version info, URLs, credentials\nbinwalk -R \"password\" firmware.bin\nbinwalk -R \"http:\u002F\u002F\" firmware.bin\n```\n\n### Step 2: Entropy Analysis\n\nAnalyze entropy to identify encrypted, compressed, and plaintext regions:\n\n```bash\n# Generate entropy plot\nbinwalk -E firmware.bin\n\n# Entropy with specific block size for higher resolution\nbinwalk -E -K 256 firmware.bin\n\n# Combined entropy and signature scan\nbinwalk -BE firmware.bin\n```\n\nInterpreting entropy values:\n- **0.0 - 1.0**: Empty or padding regions (null bytes, 0xFF fill)\n- **1.0 - 5.0**: Plaintext data, code, ASCII strings, configuration\n- **5.0 - 7.0**: Compressed data (gzip, LZMA, zlib)\n- **7.0 - 7.99**: Strongly compressed or encrypted data\n- **~8.0**: Maximum entropy, likely encrypted or random data\n\n### Step 3: Extract Embedded Files\n\nExtract all identified components from the firmware image:\n\n```bash\n# Automatic extraction of known file types\nbinwalk -e firmware.bin\n\n# Recursive extraction (matryoshka mode) for nested archives\nbinwalk -Me firmware.bin\n\n# Recursive extraction with depth limit\nbinwalk -Me -d 5 firmware.bin\n\n# Extract specific file type with custom handler\nbinwalk -D \"squashfs filesystem:squashfs:unsquashfs %e\" firmware.bin\n\n# Manual extraction of data at a known offset\ndd if=firmware.bin of=extracted.squashfs bs=1 skip=327680 count=4194304\n```\n\n### Step 4: Mount and Inspect Extracted Filesystems\n\nMount extracted filesystems for deep inspection:\n\n```bash\n# Mount SquashFS filesystem\nmkdir \u002Ftmp\u002Fsquashfs_root\nunsquashfs -d \u002Ftmp\u002Fsquashfs_root extracted.squashfs\n\n# Mount CramFS filesystem\nmkdir \u002Ftmp\u002Fcramfs_root\nmount -t cramfs -o loop extracted.cramfs \u002Ftmp\u002Fcramfs_root\n\n# Extract JFFS2 filesystem\njefferson extracted.jffs2 -d \u002Ftmp\u002Fjffs2_root\n\n# Inspect the extracted filesystem\nls -la \u002Ftmp\u002Fsquashfs_root\u002F\nfind \u002Ftmp\u002Fsquashfs_root -name \"*.conf\" -o -name \"*.cfg\" -o -name \"*.key\"\nfind \u002Ftmp\u002Fsquashfs_root -name \"passwd\" -o -name \"shadow\"\n```\n\n### Step 5: String Analysis and Credential Discovery\n\nSearch extracted filesystem and raw firmware for sensitive data:\n\n```bash\n# Extract all printable strings\nstrings -a firmware.bin > all_strings.txt\nstrings -n 12 firmware.bin | sort -u > long_strings.txt\n\n# Search for credentials and secrets\ngrep -rni \"password\\|passwd\\|secret\\|api_key\\|token\" \u002Ftmp\u002Fsquashfs_root\u002Fetc\u002F\ngrep -rni \"BEGIN.*PRIVATE KEY\" \u002Ftmp\u002Fsquashfs_root\u002F\n\n# Find hardcoded URLs and endpoints\ngrep -rnoE \"https?:\u002F\u002F[a-zA-Z0-9.\u002F?=_-]+\" \u002Ftmp\u002Fsquashfs_root\u002F\n\n# Search for certificate files\nfind \u002Ftmp\u002Fsquashfs_root -name \"*.pem\" -o -name \"*.crt\" -o -name \"*.key\" -o -name \"*.p12\"\n\n# Identify busybox and service versions\nstrings \u002Ftmp\u002Fsquashfs_root\u002Fbin\u002Fbusybox | grep \"BusyBox v\"\ncat \u002Ftmp\u002Fsquashfs_root\u002Fetc\u002Fbanner 2>\u002Fdev\u002Fnull\n```\n\n### Step 6: Generate Firmware Analysis Report\n\nCompile comprehensive extraction and analysis findings:\n\n```\nReport should include:\n- Firmware metadata (vendor, model, version, build date)\n- Identified components with offsets and sizes (bootloader, kernel, filesystem, config)\n- Entropy analysis summary with regions of interest\n- Extracted filesystem structure and key contents\n- Discovered credentials, keys, certificates\n- Identified services, daemons, and their versions\n- Known CVEs applicable to identified component versions\n- Recommendations for hardening or vulnerability remediation\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **Firmware** | Software embedded in hardware devices providing low-level control; typically contains a bootloader, kernel, root filesystem, and configuration data |\n| **Entropy Analysis** | Statistical measurement of randomness in binary data; high entropy indicates encryption or compression, low entropy indicates plaintext or structured data |\n| **SquashFS** | Read-only compressed filesystem commonly used in embedded Linux devices; supports LZMA, gzip, LZO, and zstd compression |\n| **Magic Bytes** | Known byte sequences at fixed offsets that identify file types; binwalk uses a database of magic signatures to detect embedded files |\n| **Matryoshka Extraction** | Recursive extraction mode where binwalk re-scans extracted files for additional embedded content, handling deeply nested archives |\n| **CramFS** | Compressed ROM filesystem designed for embedded systems with limited flash storage; supports only zlib compression |\n| **JFFS2** | Journalling Flash File System version 2, designed for NOR and NAND flash memory in embedded devices |\n\n## Tools & Systems\n\n- **binwalk**: Primary firmware analysis tool for signature scanning, entropy analysis, and automated extraction of embedded files\n- **unsquashfs**: SquashFS extraction utility for mounting read-only compressed filesystems found in router and IoT firmware\n- **jefferson**: Python tool for extracting JFFS2 flash filesystem images commonly found in embedded devices\n- **sasquatch**: Patched SquashFS utility supporting non-standard vendor-modified SquashFS variants\n- **firmware-mod-kit**: Toolkit for extracting, modifying, and repacking firmware images for security testing\n\n## Common Scenarios\n\n### Scenario: Extracting and Auditing Router Firmware for Hardcoded Credentials\n\n**Context**: A security researcher is performing an authorized assessment of a consumer router. The firmware update file was downloaded from the vendor's support page. The goal is to identify hardcoded credentials, insecure default configurations, and known vulnerable components.\n\n**Approach**:\n1. Run `binwalk -e firmware.bin` to perform initial extraction\n2. Use `binwalk -E firmware.bin` to check entropy and identify encrypted regions\n3. Locate the SquashFS root filesystem in the extracted output\n4. Mount with `unsquashfs` and inspect `\u002Fetc\u002Fpasswd`, `\u002Fetc\u002Fshadow`, and web server configs\n5. Search for hardcoded credentials with `grep -rni \"password\" \u002Ftmp\u002Froot\u002Fetc\u002F`\n6. Identify service versions and cross-reference with CVE databases\n7. Check for debug interfaces (telnet, UART, JTAG references) in startup scripts\n8. Examine web application code for authentication bypass or command injection\n\n**Pitfalls**:\n- Some vendors use non-standard SquashFS with custom compression; use sasquatch instead of unsquashfs\n- Encrypted firmware requires decryption keys often found in bootloader or previous unencrypted versions\n- Firmware headers may need to be stripped before binwalk can identify the embedded filesystem\n- Obfuscated strings may evade simple grep searches; use entropy analysis to locate data blobs\n\n## Output Format\n\n```\nFIRMWARE EXTRACTION REPORT\n====================================\nFirmware:         TP-Link TL-WR841N v14\nFile:             wr841nv14_en_3_16_9_up.bin\nSize:             3,932,160 bytes (3.75 MB)\nSHA-256:          a1b2c3d4e5f6...\n\nSIGNATURE SCAN RESULTS\nOffset       Type                          Size\n------       ----                          ----\n0x00000000   U-Boot bootloader header      64 bytes\n0x00020000   LZMA compressed data          1,048,576 bytes\n0x00120000   SquashFS filesystem v4.0      2,752,512 bytes\n0x003B0000   Configuration partition       131,072 bytes\n\nENTROPY ANALYSIS\nRegion 0x000000-0x020000: 4.21 (bootloader - plaintext code)\nRegion 0x020000-0x120000: 7.89 (kernel - LZMA compressed)\nRegion 0x120000-0x3B0000: 7.45 (filesystem - SquashFS compressed)\nRegion 0x3B0000-0x3C0000: 1.12 (config - mostly empty)\n\nEXTRACTED FILESYSTEM\nRoot filesystem: SquashFS v4.0, LZMA compression\nTotal files: 847\nTotal dirs: 112\nBusyBox version: 1.19.4\n\nSECURITY FINDINGS\n[CRITICAL] Hardcoded root password in \u002Fetc\u002Fshadow (hash: $1$...)\n[HIGH]     Telnet daemon enabled by default in \u002Fetc\u002Finit.d\u002FrcS\n[HIGH]     Private RSA key at \u002Fetc\u002Fssl\u002Fprivate\u002Fserver.key\n[MEDIUM]   BusyBox 1.19.4 (CVE-2021-42373, CVE-2021-42374)\n[MEDIUM]   Dropbear SSH 2014.63 (CVE-2016-3116)\n[LOW]      UPnP service enabled by default\n```\n",{"cve":44,"name":5,"tags":48,"capec":51,"model":52,"tools":53,"domain":38,"maxTurns":57,"nist_csf":58,"subdomain":33,"description":7},[45,46,47],"CVE-2021-42373","CVE-2021-42374","CVE-2016-3116",[20,22,49,35,50,36],"extraction","IoT-security",[],"sonnet",[54,32,55,56],"Read","Glob","Grep",20,[59,60,61],"ID.RA-01","PR.PS-01","DE.AE-02","main","a91f1293287ffa9f4f1b8f486cd6e835a1568c84","skills\u002Flinux\u002Fhardware\u002Ffirmware\u002Fbinwalk\u002Fdetect","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace","https:\u002F\u002Fgithub.com\u002FDCx7C5","#Python","2026-09-01 11:21:00",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add DCx7C5\u002Fai-marketplace --skill hardware-firmware-binwalk-detect",{"tool":75,"command":76},"bunx","bunx skills add DCx7C5\u002Fai-marketplace --skill hardware-firmware-binwalk-detect",{"tool":78,"command":79},"pnpm","pnpm dlx skills add DCx7C5\u002Fai-marketplace --skill hardware-firmware-binwalk-detect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Flinux\u002Fhardware\u002Ffirmware\u002Fbinwalk\u002Fdetect\u002FSKILL.md",true,[83],{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"index.json","REFERENCE","参考文档",707,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Flinux\u002Fhardware\u002Ffirmware\u002Fbinwalk\u002Fdetect\u002Findex.json",[90,113,134,155,177,193],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":39},"01M71HAPZ01KQ30RKTB0FFSQ05","services-wmi-persistence-detect","Detect WMI event subscription persistence by enumerating ActiveScriptEventConsumer, CommandLineEventConsumer, and permanent subscriptions in the WMI repository.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fpersistence\u002Fdetect\u002FSKILL.md",[],[97,21,98,99,100,28,101,102,103,104,105,106,107,108,109,110,111,38,112],"services","services wmi persistence detect","wmi","persistence","cm","process","activescript","event","subscriptions","commandline-consumer","repository","subscription","event-subscription","t1546.003","forensics","process-forensics",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":39},"01M71HAK6JTTTS229T17WJMMCG","services-wmi-exec-exploit","Perform lateral movement across Windows networks using WMI-based remote execution techniques including Impacket wmiexec.py, CrackMapExec, and native WMI commands for stealthy post-exploitation during red team engagements.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fexec\u002Fexploit\u002FSKILL.md",[],[120,97,121,99,122,123,124,38,32,34,125,126,127,128,28,129,130,131,132,133],"exploit","services wmi exec exploit","exec","remote","traffic","team","across","crackmapexec","native","command","lateral movement","read","lateral-movement","Impacket",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":39},"01M71HAG6MHKNQV8KDZKMT4886","registry-artifact-extract","Extract and analyze Windows Registry hives to uncover user activity, installed software, autostart entries, and evidence of system compromise.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fregistry\u002Fartifact\u002Fextract\u002FSKILL.md",[],[141,142,143,144,145,146,38,32,147,34,148,149,28,131,150,151,152,153,154,52],"artifact","registry","registry artifact extract","extract","evidence-collection","artifact-analysis","collection","analyze","uncover","software","activity","digital-forensics","windows-registry","regripper",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":39},"01M71HACR4A8XTWTTSXK4124AA","processes-token-impersonate-detect","Detect Windows token impersonation and privilege abuse including SeImpersonatePrivilege exploitation via Potato attacks and token stealing techniques.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Ftoken\u002Fimpersonate\u002Fdetect\u002FSKILL.md",[],[21,162,163,164,165,166,167,101,168,38,112,169,170,171,172,173,174,175,176,28],"processes token impersonate detect","token","processes","attacks","windows","escalation","techniques","privilege-escalation","seimpersonate","token-impersonation","printspoofer","exploitation","potato","impersonation","via",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":39},"01M71HAABSB4Z6QFSXEG00R4RK","processes-thread-injection-detect","Detect Windows thread injection techniques including CreateRemoteThread, QueueUserAPC, NtCreateThreadEx, and thread hijacking via process memory analysis.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fthread\u002Finjection\u002Fdetect\u002FSKILL.md",[],[184,185,21,186,164,166,187,101,188,168,38,112,34,189,190,191,192,176,28,102],"thread","processes thread injection detect","injection","memory","process-injection","api","apc-injection","thread-injection","nt-api",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":199,"publishedAt":39},"01M71HA7H311V5G14WMX58HQSS","processes-hollow-technique-detect","Detect process hollowing (RunPE) by identifying processes with mismatched image paths between PEB and VAD tree, or unmapped PE headers in memory.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fhollow\u002Ftechnique\u002Fdetect\u002FSKILL.md",[],[200,21,164,201,187,101,202,203,38,112,204,205,31,206,207,208,28,102,209,210],"processes hollow technique detect","tree","memory-forensics","process-hollow","peb","runpe","pe-header","in memory","with","mismatched","headers"]