restler
Auth/lab ref: Stateful REST API fuzzer from OpenAPI specs. For testing complex API dependency chains, producer-consumer request sequencing, and replayable bug-bucket workflows for API reliability/security testing.
v2026.11.13-21cd5683 installs+3 in 7 days39 StarsMITsynced 11 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/restlerWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package5ca93d77…5f6c3e2d
5ca93d771b72…bb4d5f6c3e2d1 file · 1.5 KBScanLow1 finding
- Links to outside domains
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/fuzzing/restler@21cd568
On this page
RESTler explores deeper API states by inferring request dependencies from OpenAPI definitions.
Workflow (Recommended Order)
- Compile: OpenAPI -> RESTler grammar.
- Test (smoke): verify setup and required dictionary values.
- Fuzz-lean: quick bug hunting baseline.
- Fuzz: deep BFS-style state exploration.
Quick Start
# Build (local)
python build-restler.py --dest_dir <restler_bin>
# Typical campaign starts with compile + test before fuzz modes
restler.exe fuzz-lean --grammar_file <grammar.py> --dictionary_file <dict.json>
restler.exe fuzz --grammar_file <grammar.py> --dictionary_file <dict.json> --time_budget 1Operator Flow
- Validate schema quality and authentication path first.
- Run
test/smoke style workflow to confirm dependencies and dictionary values. - Run
fuzz-leanfor quick risk discovery. - Run
fuzzfor deeper sequence exploration with settings file tuning. - Reproduce via replay logs and bug buckets before assigning fixes.
Practical Notes
- Always fix setup gaps discovered in
testmode before deep fuzzing. - Deep fuzzing can cause service instability/outages on weak implementations.
- Use replay logs and bug buckets for deterministic re-validation.
High-Value Settings
fuzzing_mode(bfs,bfs-cheap,random-walk,directed-smoke-test)max_sequence_length,max_combinations- include/exclude endpoint filters (
include_requests,exclude_requests,path_regex) - retry & timing controls (
custom_retry_settings,producer_timing_delay) - trace database (
use_trace_database) for structured replay workflows
Replay & Triage Pattern
- Start from
bug_buckets.txtsummary. - Open specific bucket replay log and verify request sequence.
- Replay with same auth/host settings.
- Confirm reproducibility and collect minimal sequence evidence.
- Patch server + rerun replay to verify closure.
Common Pitfalls
- Skipping auth refresh handling leads to noisy false negatives.
- Fuzzing full API surface without scope controls can burn time-budget quickly.
- Forgetting manual cleanup after replay-created resources.
Resources
- https://github.com/microsoft/restler-fuzzer
- https://github.com/microsoft/rest-api-fuzz-testing
- https://raw.githubusercontent.com/microsoft/restler-fuzzer/main/docs/user-guide/Fuzzing.md
- https://raw.githubusercontent.com/microsoft/restler-fuzzer/main/docs/user-guide/SettingsFile.md
- https://raw.githubusercontent.com/microsoft/restler-fuzzer/main/docs/user-guide/BugBuckets.md
- https://raw.githubusercontent.com/microsoft/restler-fuzzer/main/docs/user-guide/Replay.md
Files in this version
- SKILL.md3.0 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | Yes | Yes |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | Nov 13, 2026 | 21cd568 | 5ca93d77 | Signed | – |
More from AeonDave
All from this publisherMore in Reverse engineering and fuzzing
See the categoryAsk anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login