Skip to content
KitploitKITPLOIT
도구익스플로잇블로그
Log in
제출
도구익스플로잇블로그
제출

해킹, 침투 테스트 및 사이버 보안 도구를 당신의 보안 무기고에!

Kitploit은 해킹, 사이버 보안 및 침투 테스트 도구 디렉토리입니다. 최신 프로젝트 업데이트를 발견하여 취약점을 찾고, 시스템을 분석하고, 테스트를 자동화하고, 보안을 강화하세요.

피드문의개인정보© 2026 Kitploit

도구 디렉토리

카테고리

모든 카테고리 보기
Loading categories
DecodeBox — Client-side workbench that auto-detects, recursively decodes, and analyses unknown or layered data, extracting indicators and CWE-tagged security findings with evidence. | Kitploit
도구/GitHubGitHub/owasp/decodebox
Static AnalysisForensicsInformation GatheringWeb SecurityCryptographyCTFUtilities & FrameworksLearning & Education
GitHubowasp/decodebox

DecodeBox

Client-side workbench that auto-detects, recursively decodes, and analyses unknown or layered data, extracting indicators and CWE-tagged security findings with evidence.

저장소 보기
7410410일 전아직 검토되지 않음
공유
웹사이트
요청한 언어로 콘텐츠를 사용할 수 없습니다. 영어 버전을 표시합니다.

OWASP DecodeBox

OWASP Project: Incubator License Live Site Client-side

Encode. Decode. Identify.

https://github.com/user-attachments/assets/93eb8f92-7e93-4324-8d94-73d7040379f0


Project Status

Pre-release, and already usable. The workbench runs, the detection engine unwraps layered payloads, and the analysis report is complete.

  • Engine: 504 operations across data formats, ciphers, public-key cryptography, hashing, compression, networking, forensics, multimedia and extractors. Every one is covered by a round-trip or a published known-answer test — 1,167 tests in all.
  • Interface: Three modes — a workspace for transforming, a report for understanding, and a CTF mode for working out what to try next, deployed at owasp.github.io/DecodeBox.

Still ahead: the accessibility audit and the internationalisation pass. A disassembler and an OCR engine are deliberately out of scope — they are their own projects, not operations.

About The Project

The usual model for a tool like this assumes you already know what your data is: you pick the operations, you chain them, you iterate. That is fine when you recognise the format on sight, and useless when you do not — which is most of the time an analyst is looking at something new.

DecodeBox starts from the other end. You paste, and it works out what it is holding: every layer unwrapped, every indicator extracted, every security finding explained, with the evidence for each claim visible rather than asserted.

Everything runs in your browser. No input, no recipe, and no file ever leaves your machine — there is no server to send it to.

Key Objectives

  • Identify: Name unknown data rather than requiring the user to name it first.
  • Explain: Show the measurement behind every claim, so a confidence score can be checked.
  • Analyse: Report what a payload means — indicators and security findings at every depth — not only what its bytes say.
  • Guarantee: Keep the processing entirely client-side, and enforce that in the build rather than promising it in a document.

See it in Action

A real payload from the test suite: Base64 over Base64 over gzip over JSON, with a PowerShell loader in one field.

Findings   4        Indicators 7        Layers 8        257 ms

CRITICAL  Cloud or service credential            CWE-798
          Input → Base64 → Base64 → gzip
          AKIAIOSFODNN7EXAMPLE

CRITICAL  PowerShell download-and-execute        CWE-94
          Input → Base64 → Base64 → gzip → JSON → Base64 → UTF-16LE
          IEX (New-Object Net.WebClient).DownloadString

The second finding is six layers down, and the last hop came from a Base64 blob inside one JSON field. Nothing that greps the original blob sees it, and nothing that unwraps a single linear chain reaches it.

How It Works

  1. Detect. Candidate interpretations are scored from independent signals — Shannon entropy, character set, length rules, magic bytes, and whether the decoded result is itself well-formed. Each signal carries a human-readable justification, and the last one carries the most weight: any long hex string is shaped like Base64, but only one reading decodes to something coherent.
  2. Unwrap. The best candidate is decoded and detection runs again on the result, building a tree rather than a chain — including encoded regions buried inside structures. The recursion is bounded on depth, node count and wall-clock time.
  3. Terminate, and say why. A chain ends on content, on a named one-way value (Base64 → Base64 → MD5), on a remainder that cannot be decoded such as a JWT signature, or on an honest admission that a limit was reached and there may be more underneath.
  4. Scan. Indicators and security findings are gathered from every node of the tree, each reported with a CWE reference, the evidence, and the exact decode path that revealed it.

When nothing declared explains the input, DecodeBox tries every single-byte XOR key and every rotation and scores each result for readability — at a confidence that says plainly it was a search rather than a match.

Security & Privacy

DecodeBox processes untrusted, deliberately malformed input by design.

  • No backend. There is nothing to breach, nothing to log, and nothing to subpoena.
  • No network, enforced. The build ships a Content Security Policy with connect-src 'none' and script-src 'self' plus a hash for the one inline script. Fonts are bundled rather than fetched, and the build fails if a CDN reference ever appears in the output.
  • No dynamic evaluation. eval, new Function, and any path that renders input as HTML are forbidden by lint rules, not by convention.

style-src does allow 'unsafe-inline', because React writes inline style attributes; script-src, where the real risk lives, stays strict. To report a vulnerability, see SECURITY.md — please do not open a public issue for security reports.

Repository Structure

DecodeBox/
├── .github/workflows/   # CI, CodeQL, SBOM, markdown quality, Pages deployment
├── public/              # Bundled fonts, favicon, CNAME
├── src/
│   ├── engine/          # The analysis engine — the only half that knows about data
│   │   ├── index.ts     # THE SEAM — the only module the interface imports from
│   │   ├── operations/  # One self-contained module per transformation
│   │   ├── detection/   # Entropy, charset, magic bytes, structural validity
│   │   ├── analysis/    # Recursive exploration, indicators, security findings
│   │   ├── ctf/         # Flag search, cipher key recovery, ranked hints
│   │   ├── core/        # Recipe executor, byte handling, ciphers, codecs
│   │   └── worker/      # The engine off the main thread, past a size threshold
│   ├── components/      # The interface: workspace, report, CTF mode
│   ├── store/           # One zustand store
│   ├── hooks/           # Interaction logic shared across components
│   ├── lib/             # Share links, saved recipes, recipe text format
│   ├── i18n/            # Every user-facing string
│   └── styles/          # Design tokens and themes
├── SECURITY.md
└── LICENSE

The interface reaches the engine through one narrow facade exposing seven functions — listOperations, bake, detect, autoDecode, identify, analyse and hints. Both halves can be developed, tested and replaced independently; the workspace was once rebuilt from scratch without the engine changing by a line. Adding an operation should never require touching the UI.

Quick Start

Requires Node.js 22.12 or later. CI builds on 22 and 24; .nvmrc pins 22 for development.

npm install
npm run dev     # development server
npm run test    # 1,167 tests
npm run build   # static site in dist/

The build output is fully static — no runtime, no server, no environment variables. Any static host will serve it.

One File, No Install

There is a Download DecodeBox button in the header of the running application. It hands you decodebox.html: the whole thing in a single 1.2 MB file — the interface, all 504 operations, the fonts, the styles. Double-click it and it runs. No server, no npm, no network, nothing to install, which is the point on an air-gapped machine where getting a build toolchain in is harder than getting one file in.

npm run build produces it alongside the site, so any deployment serves it:

도구 다운로드

인기

모두 보기 →

커뮤니티에서 가장 많이 사용되는 도구를 찾아보세요.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 궁극의 OSINT 툴킷: 조사 그래프, 신뢰도 점수 산정, 별칭 패밀리, 지도, 타임라인 및 보고서. 49개 모듈, 400개 이상 사이트, API 키 불필요.

    772
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    # GhostLock 원탭 실행 앱 (CVE-2026-43499)

    505
  • 3

    ARTEX

    baarai/artex

    LLM 멀티 에이전트 자율 침투 테스트 플랫폼으로, 플래너/워커 에이전트, 자산 및 탐색 그래프, MITM 트래픽 기록, 취약점 재테스트 기능을 제공합니다.

    420
  • 4

    redforge

    cybersecurity91/redforge

    브라우저 측 레드 팀 툴킷으로, 정찰, 페이로드 생성, 자격 증명 공격, 암호화, 인코딩 및 참여 보고를 위한 102개의 오프라인 도구를 제공합니다.

    345
  • 5

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    AI 네이티브 사이버보안을 위한 행동 체계—의도가 통제된 실행이 되고, 증거가 운영 메모리가 되며, 모든 운영이 다음 운영을 개선하는 곳.

    260
  • 6

    antifox

    antifox-ai/antifox

    정찰, 공격 표면 탐색, 익스플로잇 검증, 증거 기반 보고서 전달을 수행하는 AI 멀티 에이전트 자율 침투 테스트 플랫폼입니다.

    251

모든 도구 탐색

도구 컬렉션을 둘러보세요

모든 도구 보기 →