Can I export curl snippets with the corrupted JSON?

Yes. Copy the payload from the corruption report or download the JSON directly for integration tests.

How do I focus on numeric drift?

Use Random Byte Mutation at low intensity to flip numeric characters without destroying structure.

Will this trigger my WAF?

Likely - and that's valuable. Capture the alert telemetry to prove coverage.

Can I simulate JSON Lines corruption?

Yes. Upload newline-delimited JSON; Hexwilt will mutate across line boundaries for ingestion stress tests.

Does Hexwilt support schema-aware corruption?

While corruption is byte-level today, you can pair results with your schema tooling to highlight violated fields.

The browser app mirrors our CLI, so every corruption mode can be reproduced headlessly using the same seed.

API Resilience

Fuzz JSON payloads without custom scripts

Break braces, reorder keys, or inject noise into payloads to see how your services and observability stack react.

11Common JSON failure modes bundled into presets

Extensions: .json

Why corrupt a JSON file?

JSON feeds every modern API. One missing brace or rogue NaN can cascade into outages. Hexwilt delivers curated corruption patterns that mimic the wild world of client bugs and hostile input.

Flip structural characters without writing Python scripts.
Simulate high-entropy payloads to trigger WAF and schema defenses.
Replay exact mutations across CI pipelines with deterministic seeds.

Corruption checklist

1.Load a JSON fixture from staging.
2.Choose Byte Flip for subtle drift or Random Byte Mutation for catastrophic failures.
3.Send the output through your API gateway, CLI, or queue consumer.

Common failure modes

Malformed syntax

APIs return 400/500 responses when braces, commas, or quotes are removed.

Type drift

Numbers turn into strings or booleans, stress-testing contract enforcement.

Deep nesting overflow

Recursive noise pushes parser depth limits, great for DoS resilience checks.

What corruption unlocks

Contract testing

Ensure schema validators catch mutated payloads before they hit business logic.

Security research

Simulate hostile input without spinning up dedicated fuzzers.

Support runbooks

Give customer support teams corrupted payloads to replicate user-facing bugs quickly.

Recommended corruption modes

Byte Flip

Byte Flip mutates targeted byte ranges while respecting overall file length. It is ideal when you want the file to open - but misbehave - surfacing nuanced defects like off-by-one errors, glitchy renders, or schema drift.

Learn about Byte Flip

Random Byte Mutation

When you want maximum variability, choose Random Byte Mutation. It sprinkles mutations across the entire file, from metadata to payload, revealing assumptions you did not know existed.

Learn about Random Byte Mutation

Entropy Surge

Need to practice ransomware recovery without detonating malware? Entropy Surge is your mode. It blasts targeted regions with high-entropy bytes so signature-based detection, backup validation, and forensic training all get realistic input.

Learn about Entropy Surge

Use it during these workflows

API gateway hardening

Verify rate limits, schema checks, and alerting when corrupted payloads arrive.

Observability drills

Confirm logs, traces, and dashboards tell a coherent story when JSON decoding fails.

Developer onboarding

Teach new engineers about failure modes with real corrupted samples.

QA tips

Record HTTP responses and error codes for regression packs.
Pair corrupted JSON with expected schema diffs to highlight contract violations.
Use low intensity runs to mimic real-world user typos without total failure.

Compliance insight

No payloads leave your network. Hexwilt mutates JSON within the browser - ideal for PII-laden test fixtures.

JSON FAQ

Answers to the questions QA, security, and support teams ask most when corrupting JSON files.

Ready to corrupt a JSON file?

Run a safe demo below or bring your own file. Every corruption stays on your device and ships with a replayable report.