Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
aeondave/jazzerReverse engineering and fuzzing

jazzer

⁨Auth/lab ref: Coverage-guided in-process fuzzing for JVM (Java/Kotlin/etc), based on libFuzzer concepts.⁩

v2026.11.13-21cd5682 installs+2 in 7 days39 StarsApache-2.0synced 11 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/jazzer

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
zt75dwLNIw…1OE1lsBA==The CLI checks the SHA-256 and the signature before it writes a file.
Package2105814a…e2769013
2105814a3d1d…7904e27690131 file · ⁦1.4 KB⁩
ScanLow1 finding
  • Links to outside domains
See the full scan
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/fuzzing/jazzer@21cd568

JVM-native fuzzing engine with @FuzzTest workflow and built-in security bug detectors.

Quick Start

xml
<!-- pom.xml -->
<dependency>
  <groupId>com.code-intelligence</groupId>
  <artifactId>jazzer-junit</artifactId>
  <version>LATEST</version>
</dependency>
java
@FuzzTest
void fuzzDecode(String input) {
  assertEquals(input, decode(encode(input)));
}
bash
# Fuzzing mode
JAZZER_FUZZ=1 mvn test

Operator Flow

  1. Start with JUnit @FuzzTest in a narrow API surface.
  2. Seed meaningful examples (parameter sources + existing regression inputs).
  3. Run fuzz mode to discover, then store crash inputs under test resources.
  4. Keep regression mode in CI to prevent bug reintroduction.
  5. Expand instrumentation scope only when throughput remains acceptable.

Key Points

  • Regression mode by default; fuzz mode via env var.
  • Stores generated corpus and crashing inputs in predictable directories.
  • Includes bug detectors (e.g., SSRF / path traversal / command injection classes).

Practical Tricks

  • Use annotations (@WithUtf8Length, @InRange, etc.) to constrain data and improve signal density.
  • Tune run duration with maxDuration / max_total_time style controls.
  • Configure instrumentation includes/excludes to avoid useless classpath overhead.
  • Explicitly manage detector hooks if false positives appear in complex multi-thread setups.

Common Pitfalls

  • One giant fuzz test that mixes unrelated APIs reduces triage quality.
  • Ignoring corpus path conventions causes lost regressions.
  • Treating finder output as final root cause without replaying and minimizing reproducer.

Configuration Notes

  • Option precedence matters: defaults < env vars < system properties < JUnit params < CLI.
  • For standalone mode, verify classpath and target class/method wiring first.

Resources

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesYesYes
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.11.13-21cd568Nov 13, 202621cd5682105814aSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login