Vai al contenuto
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/mythrilReverse engineering e fuzzing

mythril

⁨Auth/lab ref: symbolic-execution-based security analyzer for Solidity and EVM bytecode.⁩

v2026.11.13-21cd5682 installazioni+2 in 7 giorni39 StelleMITsincronizzato 11 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

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

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
5Y4wX0sEhg…NS/kOjCQ==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto2b65e7b2…038640d2
2b65e7b22c80…757a038640d21 file · ⁦1.3 KB⁩
ScansioneBassonessuna segnalazione
La scansione non ha trovato nulla da segnalare in questa versione.Vedi la scansione completa
Sorgentegithub.com/AeonDave/malskill/tree/main/offensive-tools/vuln-scanners/mythril@21cd568

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

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

bash
# Docker (upstream-recommended simple path)
docker pull mythril/myth

# Classic pip path
pip3 install mythril

Quick Start

bash
# Analyze Solidity source
myth analyze Contract.sol

# Analyze deployed contract by address
myth analyze -a 0xDEADBEEF...

# Limit transaction depth
myth analyze Contract.sol -t 3

Core Workflow

1. Run a bounded analysis

bash
myth analyze Contract.sol -t 3 --execution-timeout 60

Use 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 slither pass
  • 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.

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellSìSì
Usa la reteNoNo
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

La scansione non ha trovato nulla da segnalare in questa versione.

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.11.13-21cd56813 nov 202621cd5682b65e7b2Firmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login