How to conduct value-centric Web3 red teaming using the MITRE AADAPT framework. Use this skill whenever the user mentions Web3 security, blockchain red teaming, smart contract testing, DeFi security, oracle manipulation, flash loan attacks, cross-chain security, or wants to test crypto infrastructure against economic attacks. This skill helps inventory value-bearing components, map them to AADAPT techniques, design attack scenarios, and set up detection telemetry.
This skill guides you through conducting red team exercises that test whether Web3 infrastructure can resist irreversible economic loss. The MITRE AADAPT (Adversarial Actions in Digital Asset Payment Techniques) framework focuses on attacker behaviors that manipulate digital value rather than just infrastructure.
When to Use This Skill
Use this skill when:
Planning or executing Web3/blockchain security assessments
Testing DeFi protocols, bridges, oracles, or smart contracts
Designing red team scenarios for crypto infrastructure
Setting up detection and monitoring for blockchain systems
Evaluating governance, signing, or upgrade mechanisms
The user mentions any of: flash loans, oracle manipulation, cross-chain attacks, smart contract security, DeFi red teaming, blockchain penetration testing
Core Methodology
Phase 1: Inventory Value-Bearing Components
Build a complete map of everything that can influence value state, on-chain and off-chain.
What to inventory:
Custodial signing services
HSM/KMS clusters, Vault/KMaaS, signing APIs
Key IDs, policies, automation identities
Approval workflows and authorization chains
Admin & upgrade paths
Proxy admins, governance timelocks
Emergency pause keys, parameter registries
Who/what can call them, quorum requirements, delays
Map each step to specific AADAPT techniques plus observables
Formulate and deploy detection hypotheses
Re-run until MTTD and MTTC meet business tolerances
Track maturity on three axes:
Visibility: Every critical value path has telemetry in each plane
Coverage: Proportion of prioritized AADAPT techniques exercised end-to-end
Response: Ability to pause contracts, revoke keys, or freeze flows before irreversible loss
Scenario Templates
Use these repeatable blueprints to design simulations:
Scenario A: Flash-Loan Economic Manipulation
Objective: Borrow transient capital inside one transaction to distort AMM prices/liquidity and trigger mispriced borrows, liquidations, or mints before repaying.
Execution:
Fork the target chain and seed pools with production-like liquidity
Borrow large notional via flash loan
Perform calibrated swaps to cross price/threshold boundaries relied on by lending, vault, or derivative logic
Invoke the victim contract immediately after the distortion (borrow, liquidate, mint) and repay the flash loan
Measurement:
Did the invariant violation succeed?
Were slippage/price-deviation monitors, circuit breakers, or governance pause hooks triggered?
How long until analytics flagged the abnormal gas/call graph pattern?
1---2name: web3-red-teaming-aadapt3description: How to conduct value-centric Web3 red teaming using the MITRE AADAPT framework. Use this skill whenever the user mentions Web3 security, blockchain red teaming, smart contract testing, DeFi security, oracle manipulation, flash loan attacks, cross-chain security, or wants to test crypto infrastructure against economic attacks. This skill helps inventory value-bearing components, map them to AADAPT techniques, design attack scenarios, and set up detection telemetry.4metadata:5 source: https://skillmd.com/skills/abelrguezr/web3-red-teaming-aadapt6---78# Value-Centric Web3 Red Teaming (MITRE AADAPT)910This skill guides you through conducting red team exercises that test whether Web3 infrastructure can resist irreversible economic loss. The MITRE AADAPT (Adversarial Actions in Digital Asset Payment Techniques) framework focuses on attacker behaviors that manipulate digital value rather than just infrastructure.1112## When to Use This Skill1314Use this skill when:15- Planning or executing Web3/blockchain security assessments16- Testing DeFi protocols, bridges, oracles, or smart contracts17- Designing red team scenarios for crypto infrastructure18- Setting up detection and monitoring for blockchain systems19- Evaluating governance, signing, or upgrade mechanisms20- The user mentions any of: flash loans, oracle manipulation, cross-chain attacks, smart contract security, DeFi red teaming, blockchain penetration testing2122## Core Methodology2324### Phase 1: Inventory Value-Bearing Components2526Build a complete map of everything that can influence value state, on-chain and off-chain.2728**What to inventory:**29301. **Custodial signing services**31 - HSM/KMS clusters, Vault/KMaaS, signing APIs32 - Key IDs, policies, automation identities33 - Approval workflows and authorization chains34352. **Admin & upgrade paths**36 - Proxy admins, governance timelocks37 - Emergency pause keys, parameter registries38 - Who/what can call them, quorum requirements, delays39403. **On-chain protocol logic**41 - Lending, AMMs, vaults, staking, bridges, settlement rails42 - Document invariants: oracle prices, collateral ratios, rebalance cadence43444. **Off-chain automation**45 - Market-making bots, CI/CD pipelines, cron jobs, serverless functions46 - API keys, service principals that request signatures47485. **Oracles & data feeds**49 - Aggregator composition, quorum, deviation thresholds, update cadence50 - Every upstream relied on by automated risk logic51526. **Bridges and cross-chain routers**53 - Lock/mint contracts, relayers, settlement jobs54 - Chains or custodial stacks being tied together5556**Deliverable:** A value-flow diagram showing how assets move, who authorizes movement, and which external signals influence business logic.5758### Phase 2: Map Components to AADAPT Behaviors5960Translate the AADAPT taxonomy into concrete attack candidates per component:6162| Component | Primary AADAPT Focus |63|-----------|---------------------|64| Signing/KMS estates | Credential theft, policy bypass, signing-abuse, governance takeover |65| Oracles/feeds | Input poisoning, aggregation manipulation, deviation-threshold evasion |66| On-chain protocols | Flash-loan economic manipulation, invariant breaking, parameter reconfiguration |67| Automation pipelines | Compromised bot/CI identities, batch replay, unauthorized deployment |68| Bridges/routers | Cross-chain evasion, rapid hop laundering, settlement desynchronization |6970### Phase 3: Prioritize by Feasibility vs Impact7172**Operational weaknesses** (start here - could succeed today):73- Exposed CI credentials74- Over-privileged IAM roles75- Misconfigured KMS policies76- Automation accounts that can request arbitrary signatures77- Public buckets with bridge configs7879**Value-specific weaknesses** (deeper protocol attacks):80- Fragile oracle parameters81- Upgradable contracts without multi-party approvals82- Flash-loan sensitive liquidity83- Governance actions that bypass timelocks8485Work the queue like an adversary: start with operational footholds, then progress into deep protocol/economic manipulation paths.8687### Phase 4: Execute in Controlled Environments8889**Environment setup:**90- Forked mainnets or isolated testnets91- Replicate bytecode, storage, and liquidity92- Enable flash-loan paths, oracle drifts, and bridge flows end-to-end93- Never touch real funds9495**Blast-radius planning:**96- Define circuit breakers and pausable modules97- Prepare rollback runbooks98- Use test-only admin keys99100**Coordination:**101- Notify custodians, oracle operators, bridge partners, compliance102- Ensure monitoring teams expect the traffic103- Document scope, authorization, and stop conditions104105### Phase 5: Instrument Telemetry106107Align telemetry streams so every scenario produces actionable detection data:108109**Chain-level traces:**110- Full call graphs, gas usage, transaction nonces, block timestamps111- Reconstruct flash-loan bundles, reentrancy-like structures, cross-contract hops112113**Application/API logs:**114- Tie each on-chain tx to human or automation identity115- Session ID, OAuth client, API key, CI job ID, IPs, auth methods116117**KMS/HSM logs:**118- Key ID, caller principal, policy result, destination address, reason codes119- Baseline change windows and high-risk operations120121**Oracle/feed metadata:**122- Per-update data source composition, reported value123- Deviation from rolling averages, thresholds triggered, failover paths124125**Bridge/swap traces:**126- Correlate lock/mint/unlock events across chains127- Correlation IDs, chain IDs, relayer identity, hop timing128129**Anomaly markers:**130- Slippage spikes, abnormal collateralization ratios131- Unusual gas density, cross-chain velocity132133Tag everything with scenario IDs or synthetic user IDs.134135### Phase 6: Purple-Team Loop1361371. Run the scenario in the controlled environment1382. Capture detections (alerts, dashboards, responders paged)1393. Map each step to specific AADAPT techniques plus observables1404. Formulate and deploy detection hypotheses1415. Re-run until MTTD and MTTC meet business tolerances142143**Track maturity on three axes:**144- **Visibility:** Every critical value path has telemetry in each plane145- **Coverage:** Proportion of prioritized AADAPT techniques exercised end-to-end146- **Response:** Ability to pause contracts, revoke keys, or freeze flows before irreversible loss147148## Scenario Templates149150Use these repeatable blueprints to design simulations:151152### Scenario A: Flash-Loan Economic Manipulation153154**Objective:** Borrow transient capital inside one transaction to distort AMM prices/liquidity and trigger mispriced borrows, liquidations, or mints before repaying.155156**Execution:**1571. Fork the target chain and seed pools with production-like liquidity1582. Borrow large notional via flash loan1593. Perform calibrated swaps to cross price/threshold boundaries relied on by lending, vault, or derivative logic1604. Invoke the victim contract immediately after the distortion (borrow, liquidate, mint) and repay the flash loan161162**Measurement:**163- Did the invariant violation succeed?164- Were slippage/price-deviation monitors, circuit breakers, or governance pause hooks triggered?165- How long until analytics flagged the abnormal gas/call graph pattern?166167### Scenario B: Oracle/Data-Feed Poisoning168169**Objective:** Determine whether manipulated feeds can trigger destructive automated actions (mass liquidations, incorrect settlements).170171**Execution:**1721. In the fork/testnet, deploy a malicious feed or adjust aggregator weights/quorum/update cadence beyond tolerated deviation1732. Let dependent contracts consume the poisoned values and execute their standard logic174175**Measurement:**176- Feed-level out-of-band alerts177- Fallback oracle activation178- Min/max bound enforcement179- Latency between anomaly onset and operator response180181### Scenario C: Credential/Signing Abuse182183**Objective:** Test whether compromising a single signer or automation identity enables unauthorized upgrades, parameter changes, or treasury drains.184185**Execution:**1861. Enumerate identities with sensitive signing rights (operators, CI tokens, service accounts invoking KMS/HSM, multisig participants)1872. Simulate compromise (re-use their credentials/keys within the lab scope)1883. Attempt privileged actions: upgrade proxies, change risk parameters, mint/pause assets, or trigger governance proposals189190**Measurement:**191- Do KMS/HSM logs raise anomaly alerts (time-of-day, destination drift, burst of high-risk operations)?192- Can policies or multisig thresholds prevent unilateral abuse?193- Are throttles/rate limits or additional approvals enforced?194195### Scenario D: Cross-Chain Evasion & Traceability Gaps196197**Objective:** Evaluate how well defenders can trace and interdict assets rapidly laundered across bridges, DEX routers, and privacy hops.198199**Execution:**2001. Chain together lock/mint operations across common bridges2012. Interleave swaps/mixers on each hop, maintain per-hop correlation IDs2023. Accelerate transfers to stress monitoring latency (multi-hop within minutes/blocks)203204**Measurement:**205- Time to correlate events across telemetry + commercial chain analytics206- Completeness of the reconstructed path207- Ability to identify choke points for freezing in a real incident208- Alert fidelity for abnormal cross-chain velocity/value209210## Quick Start Checklist211212When starting a Web3 red team engagement:2132141. [ ] Complete value inventory (all 6 component categories)2152. [ ] Map components to AADAPT techniques2163. [ ] Prioritize by operational feasibility first2174. [ ] Set up forked testnet with production-like state2185. [ ] Define blast-radius controls and circuit breakers2196. [ ] Coordinate with stakeholders and get legal sign-off2207. [ ] Instrument telemetry for all value planes2218. [ ] Select and execute scenario templates2229. [ ] Run purple-team loop until MTTD/MTTC targets met22310. [ ] Document findings and detection improvements224225## References226227- [MITRE AADAPT Framework as a Red Team Roadmap (Bishop Fox)](https://bishopfox.com/blog/mitre-aadapt-framework-as-a-red-team-roadmap)228- MITRE AADAPT Matrix: https://attack.mitre.org/adapt/
Run npx get-skill add abelrguezr/web3-red-teaming-aadapt in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
How to conduct value-centric Web3 red teaming using the MITRE AADAPT framework. Use this skill whenever the user mentions Web3 security, blockchain red teaming, smart contract testing, DeFi security, oracle manipulation, flash loan attacks, cross-chain security, or wants to test crypto infrastructure against economic attacks. This skill helps inventory value-bearing components, map them to AADAPT techniques, design attack scenarios, and set up detection telemetry. It is listed under Security on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: WARNING. Capability flags: executes scripts, makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
abelrguezr (@abelrguezr) published this skill. Their other Agent Skills are listed on their SkillMD profile.