How sim0n/caesium works
Project type and purpose
• Caesium is a standalone Java desktop application (Swing‐based GUI) that performs Java bytecode obfuscation.
• It reads an input JAR (and its dependencies), applies a configurable set of “mutator” transformations on the bytecode, and emits a mutated JAR.
File structure
• Top-level: pom.xml (Maven build), .github/workflows/maven.yml (CI), README, LICENSE.
• src/main/java/dev/sim0n/caesium: core packages:
• “gui” – Swing UI classes (CGui, LibraryTab)
• “manager” – ClassManager & MutatorManager orchestration
• “mutator” – ClassMutator interface + implementations (e.g., ControlFlowMutator, StringMutator, CrasherMutator)
• “util” – Various helper modules (ASMUtil, ByteUtil, OSUtil, wrapper, classwriter)
• PreRuntime, Start, Caesium – bootstrapping and core engine
• src/main/resources: configuration (caesium.properties), logging (log4j2.xml)
README for additional insights
• Confirms a plugin-style mutator architecture.
• Emphasizes performance, dependency requirements, and UI usage flow.
a. Input/Output
• Input: User-selected JAR + external dependencies
• Output: Obfuscated JAR
b. GUI Layer
• CGui & LibraryTab: lets user pick mutators, launch “Mutate”
• Sends user choices to the Core Engine
c. Core Engine
• Start → PreRuntime → Caesium: bootstrap, load configuration, initialize managers
• ClassManager: reads class files via ASM (using CaesiumClassWriter, ClassTree)
• MutatorManager: holds available ClassMutator implementations
d. Mutator Plugins
• Each ClassMutator impl applies a specific transformation on the in-memory class tree
• May invoke utilities (ByteUtil, StringUtil, Dictionary, OSUtil)
e. Utilities & External Libraries
• ASM library (invoked via ASMUtil & classwriter)
• Logging (log4j2)
• Wrapper classes for reflection/bytecode manipulation
f. Configuration & Resources
• caesium.properties drives default settings
• log4j2.xml configures logging levels and appenders
Data flow:
1. User clicks “Mutate” → GUI calls Core Engine
2. Core Engine loads input classes → ClassManager builds ClassTree
3. MutatorManager iterates selected mutators → transforms ClassTree
4. ClassTree written out via CaesiumClassWriter & ASM → output JAR
5. GUI displays completion/failure
Architectural patterns & principles
• Plugin/Strategy pattern for mutators (ClassMutator interface + multiple impls)
• Modular separation: UI vs. Engine vs. Plugins vs. Utilities
• Single JAR monolith (no microservices)
• Clear layering: Presentation → Orchestration → Transformation → I/O