Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Einreichen
ToolsExploitsBlog
Einreichen

Hacking-, PenTest- und Cybersicherheits-Tools für Ihr Sicherheitsarsenal!

Kitploit ist ein Verzeichnis von Hacking-, Cybersicherheits- und Pentesting-Tools. Entdecken Sie die neuesten Projekt-Updates, um Schwachstellen zu finden, Systeme zu analysieren, Tests zu automatisieren und Ihre Sicherheit zu stärken.

FeedsKontaktDatenschutz© 2026 Kitploit

Tool-Verzeichnis

Kategorien

Alle Kategorien anzeigen
Loading categories
garble — Obfuscates Go builds by wrapping the Go toolchain, replacing identifiers, package paths, and position data with hashes and stripping debug and build information. | Kitploit
Tools/GitHubGitHub/burrowers/garble
Code AnalysisReverse EngineeringScripting & AutomationUtilities & FrameworksBinary AnalysisAnti-BotFingerprint Spoofing
GitHubburrowers/garble

garble

Obfuscates Go builds by wrapping the Go toolchain, replacing identifiers, package paths, and position data with hashes and stripping debug and build information.

Repository anzeigen
5.8k395162vor 4 TagenVon Kitploit geprüft
Teilen
Inhalt in der angeforderten Sprache nicht verfügbar. Englische Version wird angezeigt.

garble

Join Discord CI

go install mvdan.cc/garble@latest # or @master

Obfuscate Go code by wrapping the Go toolchain. Requires Go 1.27 or later.

garble build [build flags] [packages]

The tool also supports garble test to run tests with obfuscated code, garble run to obfuscate and execute simple programs, garble reverse to de-obfuscate text such as stack traces, and garble bug to file a pre-filled bug report. Run garble -h to see all available commands and flags.

Compiler, assembler, and linker failures retain the original diagnostics and add an automatically reversed copy when obfuscated names or filenames can be resolved. Successful build diagnostics and output from executed programs are left unchanged.

Purpose

Produce a binary that works as well as a regular build, but that has as little information about the original source code as possible.

The tool is designed to be:

  • Coupled with cmd/go, to support modules and build caching
  • Deterministic and reproducible, given the same initial source code
  • Reversible given the original source, to de-obfuscate panic stack traces

Mechanism

The tool wraps calls to the Go compiler and linker to transform the Go build, in order to:

  • Replace identifiers and package paths with short base64 hashes
  • Replace position information with short base64 hashed filenames
  • Remove all build, module, and debug information
  • Obfuscate literals and embedded files, if the -literals flag is given
  • Remove extra information, if the -tiny flag is given

The tool obfuscates all packages being built, including the standard runtime. Runtime obfuscation follows Go's supported GOOS/GOARCH targets; Garble does not maintain a narrower architecture allowlist.

Note that commands like garble build will use the go version found in your $PATH. To use different versions of Go, you can use GOTOOLCHAIN.

Use cases

A common question is why a code obfuscator is needed for Go, a compiled language. Go binaries include a surprising amount of information about the original source; even with debug information and symbol tables stripped, many names and positions remain in place for the sake of traces, reflection, and debugging.

Some use cases for Go require sharing a Go binary with the end user. If the source code for the binary is private or requires a purchase, its obfuscation can help discourage reverse engineering.

A similar use case is a Go library whose source is private or purchased. Since Go libraries cannot be imported in binary form, and Go plugins have their shortcomings, sharing obfuscated source code becomes an option. See #369.

Obfuscation can also help with aspects entirely unrelated to licensing. For example, the -tiny flag can make binaries 15% smaller, similar to the common practice in Android to reduce app sizes. Obfuscation has also helped some open source developers work around anti-virus scans incorrectly treating Go binaries as malware.

Word-list naming

Use garble -wordlist=words.txt build to replace identifier, package-path, and filename hashes with underscore-separated combinations of words.

The file contains one lowercase ASCII word per line, at most eight letters per word. Blank lines and surrounding whitespace are ignored. The list is sorted and deduplicated, so changing its order or location does not change obfuscation. It must contain between 2 and 65,536 distinct words. No dictionary is bundled.

Garble chooses the smallest word count, at least two, whose combination space contains at least 48 bits. For example, 256 words require six words per name. Underscores make combinations unambiguous, and the first letter preserves a Go identifier's exported status. Lists that could produce names longer than 128 bytes are rejected. Names are never truncated, because truncation would increase collisions. The mapping uses the same salted hash as the normal mode, without assigning names in traversal order.

The root process snapshots the list for compiler subprocesses, and its canonical contents are included in build-cache keys. Supply the same list and seed to garble reverse that you used for the build. Word names are longer than the normal hashes and can increase binary size, especially with a small dictionary.

Literal obfuscation

Using the -literals flag causes literal expressions such as strings to be replaced with more complex expressions, resolving to the same value at run-time. String literals injected via -ldflags=-X are also replaced by this flag. This feature is opt-in, as it can cause slow-downs depending on the input code.

Injected strings use the same size limits as source literals. Variables in the runtime and its dependencies are not covered. With -literals, -ldflags must be unpatterned; build commands separately if they need different injected values.

Literals used in constant expressions cannot be obfuscated, since they are resolved at compile time. This includes any expressions part of a const declaration, for example.

Note that this process can be reversed given enough effort; see #984.

Embedded file obfuscation

The -literals flag also obfuscates files included with //go:embed. It supports string, []byte, and embed.FS, including named string and byte-slice types. Garble leaves the original files untouched.

Contents are decoded at run time:

  • Embedded string and byte-slice variables are decoded during package initialization.
  • Files in an embed.FS are decoded each time they are opened. Paths, directory entries, file sizes, seeking, and ReadAt behavior are unchanged.

Embedded variables use the same obfuscation algorithms as source literals. Values larger than 2 KiB and embed.FS contents share a simpler decoder that scales to large files. Decoding adds runtime work; opening files in an embed.FS also allocates temporary buffers.

Embedded filenames remain visible. This is obfuscation, not encryption: the executable contains the decoding key, so its contents can still be recovered.

Tiny mode

With the -tiny flag, even more information is stripped from the Go binary. Position information is removed entirely, rather than being obfuscated. Runtime code which prints panics, fatal errors, and trace/debug info is removed. Many symbol names are also omitted from binary sections at link time. All in all, this can make binaries about 15% smaller.

With this flag, a panic still prints a single line, so a crash is not mistaken for a program which exited without running. A plain string panic prints panic: <token>, where the token is a hash of the message; garble -tiny reverse maps it back to the original message using the same source and seed, as long as the message is known at compile time. Panic values which are not strings are never formatted, and print panic: hidden instead. When a deferred call panics while another panic unwinds, the line reports the original panic, which is the message a regular build prints first. Fatal runtime errors stay silent. Panics can still be handled with recover as normal.

Tool herunterladen

Beliebteste

Alle anzeigen →

Entdecken Sie die meistgenutzten Tools unserer Community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 Das ultimative OSINT-Toolkit: Untersuchungsgraph, Konfidenzbewertung, Alias-Familien, Karte, Zeitleiste und Berichte. 49 Module, 400+ Websites, keine API-Schlüssel erforderlich.

    930
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    554
  • 3

    redforge

    cybersecurity91/redforge

    Browser-seitiges Red-Team-Toolkit mit 102 Offline-Tools für Recon, Payload-Generierung, Credential-Angriffe, Krypto, Encoding und Engagement-Reporting.

    354
  • 4

    ARTEX

    baarai/artex

    LLM-basierte Multi-Agenten-Plattform für autonome Penetrationstests mit Planer-/Worker-Agenten, Asset- und Explorationsgraphen, MITM-Verkehrsaufzeichnung und Schwachstellen-Retesting.

    349
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT-Plattform, die Shadowserver-Berichte in MongoDB einliest und sie als interaktive Karten, Analysen, Findings, Advisories und Executive-Dashboards wiedergibt.

    326
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    Das System der Handlung für KI-native Cybersicherheit – wo Absicht zu gesteuerter Ausführung wird, Beweise zu operativem Gedächtnis werden und jeder Einsatz den nächsten verbessert.

    289

Alle Tools erkunden

Durchsuchen Sie unsere Tool-Sammlung

Alle Tools anzeigen →