Back to Skills

defi-attack-patterns

DeFi attack pattern playbook. Use when analyzing flash loan attacks, price oracle manipulation, MEV sandwich attacks, governance exploits, bridge vulnerabilities, and token standard edge cases in decentralized finance protocols.

1,311stars179forksUpdated 7/8/2026

Security Assessment

High Risk(30/100)

Detected risks:

Agent-reviewed override(Offensive DeFi-exploitation playbook (flash loans, oracle manipulation, MEV, governance/bridge exploits). Local assessor didn't match its terminology; flagged manually from the doc's description. Genuine offensive tooling, per gotcha #7.)
Security Score30/100

About defi-attack-patterns

An offensive-security playbook in the yaklang hack-skills collection, focused on attack patterns against decentralized finance (DeFi) protocols for authorized security review and smart-contract auditing. Per its description it covers categories such as flash loan attacks, price oracle manipulation, MEV (maximal extractable value) sandwich attacks, governance exploits, cross-chain bridge vulnerabilities, and token-standard edge cases. It is framed as an expert playbook for analysts assessing the economic and logic-level security of DeFi systems, where risks often stem from protocol design and incentive structures rather than conventional code bugs. In a catalog context it is best understood as tooling for smart-contract auditors, protocol security researchers, and blue teams stress-testing their own deployments. Because the same knowledge can be misused against live protocols, it should be applied only to systems the user is authorized to test or in research and audit settings. Teams building DeFi protocols can treat the same categories as a threat-model checklist, reviewing oracle design, governance safeguards, bridge trust assumptions, and flash-loan resistance.

FAQ

What does this skill cover?

Attack patterns against DeFi protocols: flash loan attacks, price oracle manipulation, MEV sandwich attacks, governance exploits, bridge vulnerabilities, and token-standard edge cases.

Who is it for?

Smart-contract auditors, protocol security researchers, and blue teams assessing DeFi systems they are authorized to test.

How is DeFi security different from typical appsec?

Many DeFi vulnerabilities stem from protocol design, economic incentives, and composability rather than conventional code bugs, which this playbook emphasizes.

Can it be used on any protocol?

It should only be applied to protocols you are authorized to test, or in audit/research settings — not against live systems without permission.

How can builders use it defensively?

As a threat-model checklist for oracle design, governance safeguards, bridge trust assumptions, and flash-loan resistance.

Install defi-attack-patterns

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill