mythril
Auth/lab ref: symbolic-execution-based security analyzer for Solidity and EVM bytecode.
v2026.11.13-21cd5682 installs+2 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/mythrilWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package2b65e7b2…038640d2
2b65e7b22c80…757a038640d21 file · 1.3 KBScanLowno findings
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/vuln-scanners/mythril@21cd568
On this page
Symbolic execution for smart contract vulnerability discovery.
When to use Mythril
Use Mythril when you want to:
- explore vulnerable transaction sequences, not just static patterns
- analyze a Solidity file or deployed address for reachable issues
- get SWC-tagged findings with traces and state setup
- confirm whether a suspicious path is symbolically reachable
Use slither for fast repo-wide triage. Use Mythril for deeper path exploration.
Installation
# Docker (upstream-recommended simple path)
docker pull mythril/myth
# Classic pip path
pip3 install mythrilQuick Start
# Analyze Solidity source
myth analyze Contract.sol
# Analyze deployed contract by address
myth analyze -a 0xDEADBEEF...
# Limit transaction depth
myth analyze Contract.sol -t 3Core Workflow
1. Run a bounded analysis
myth analyze Contract.sol -t 3 --execution-timeout 60Use bounded depth and timeout early to avoid wasting cycles on state explosion.
2. Read findings as execution stories
Upstream output includes:
- issue title and severity
- SWC identifier
- function name and program counter
- vulnerable source location
- transaction sequence and caller chain
That trace is the real value: it shows how a condition can be reached.
3. Re-run with tighter scope when needed
If output is noisy or slow, reduce transaction depth or compare only the contract under active review.
Good Use Cases
- validating suspicious payable/destruct logic
- sanity-checking selfdestruct, auth, and call-chain issues
- triaging high-risk paths after a
slitherpass - reviewing deployed contracts when source is limited but address is known
Practical Notes
- Mythril is slower and deeper than Slither; do not start there for every repo.
- Docker is often the least painful install path.
- Combine symbolic findings with manual contract review and test reproduction.
- Use SWC IDs as starting taxonomy, not as the whole remediation story.
Caveats
- Symbolic execution can hit path explosion or timeouts quickly.
- Not every reported issue is exploitable in production context.
- Tooling around compiler/runtime versions still matters; mismatches can distort results.
Resources
No bundled scripts/, references/, or assets/.
Use upstream docs for installation edge cases, command variants, and remediation links via the SWC registry.
Files in this version
- SKILL.md2.6 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
The scan found nothing to flag in this version.
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 | 2b65e7b2 | 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