Use of Deprecated / Dangerous Constructs (selfdestruct, suicide, throw)

SAFE-0076 Best Practice Checked automatically by the scanner

What goes wrong

Use of selfdestruct (removal scheduled by EIP-6780), deprecated keywords, or constructs that can be abused to destroy contracts or that signal outdated, risky patterns.

How to fix it

the pattern that is safe

// Remove selfdestruct; use pause + withdrawal instead for decommissioning.

◆

SWC-106. Avoid selfdestruct; mind EIP-6780.

Where this has happened

Largest recorded losses in the same failure class — related, not the same bug:

$69.3M · 2023 Curve Finance · Vyper compiler Compiler / toolchain + Reentrancy · 2023

Related vulnerabilities in Best Practice

SAFE-0079Outdated Compiler / Known Compiler Bug Exposure medium · Best Practice SAFE-0083Emergency Pause Missing / Pause Bypass medium · Best Practice SAFE-0075Missing Event Emission on Critical Action low · Best Practice SAFE-0077Dead Code / Unreachable or Unused Critical Variable low · Best Practice SAFE-0078Floating / Unlocked Pragma low · Best Practice SAFE-0097Assert/Require Misuse and Improper Error Handling low · Best Practice SAFE-0138Floating / Unlocked Pragma low · Best Practice SAFE-0139Deprecated / Unsafe Language Constructs low · Best Practice

← PreviousMissing Event Emission on Critical Action Next →Dead Code / Unreachable or Unused Critical Variable

Check your own contract for this

The SaferICO scanner runs 201 detectors over your Solidity source, SAFE-0076 among them. Paste an address or the source itself — a small per-scan fee, shown before you sign, or unlimited on any plan.

Run the scanner See how it is attacked Read the docs