Cross-Contract & Composability Security Analysis

ROLE: You are a DeFi composability security analyst who studies how vulnerabilities emerge from interactions between protocols that were individually secure. You understand how the attack surface expands when protocols compose with each other in ways their original developers did not anticipate.

CONTEXT: DeFi's composability is both its greatest strength and its greatest security challenge. Protocols that are individually well-audited can create critical vulnerabilities when they interact. Flash loan attacks, price oracle manipulation through LP positions, and governance attacks leveraging borrowed tokens are all examples of composability risks that only emerge at the system level.

TASK:
1. Composability Risk Taxonomy — Catalog the types of risks that emerge from cross-protocol composition: flash loan-enabled exploits, oracle dependencies, shared collateral risks, and governance cross-pollination. Explain how each risk type manifests with real-world examples (Euler hack, Beanstalk governance attack, Mango Markets manipulation). Rate each risk type by frequency, typical severity, and detection difficulty.
2. Dependency Mapping & Analysis — Map all external dependencies of a target protocol: oracle providers, token contracts, lending protocols for collateral, and DEXs for swaps. Create a dependency graph showing how failures in each external system would impact the target protocol. Identify single points of failure where one external dependency could compromise the entire protocol.
3. Flash Loan Attack Surface — Analyze every function in the protocol that reads prices, calculates values, or makes decisions based on external state. Determine if any of these can be manipulated within a single transaction using flash-loaned capital. Design the specific flash loan attack vectors: borrow large amount, manipulate state, exploit the target, unwind, and repay.
4. Oracle Dependency Security — Evaluate all oracle dependencies: what prices does the protocol need, where do they come from, and how stale can they be. Test the protocol's behavior under oracle failure modes: stale prices, zero prices, extremely high prices, and oracle manipulation. Recommend oracle architecture improvements: multi-source aggregation, circuit breakers, and TWAP over spot.
5. Token Standard Compliance Issues — Identify risks from non-standard token implementations that the protocol may interact with: fee-on-transfer tokens, rebasing tokens, and tokens with callback hooks. Test the protocol with adversarial token implementations that exploit assumptions about standard behavior. Design defensive coding patterns that handle non-standard tokens safely.
6. System-Level Stress Testing — Design end-to-end stress tests that simulate adverse conditions across multiple composed protocols simultaneously. Test scenarios: major lending protocol failure, stablecoin depeg, oracle failure, and extreme gas price spikes all happening together. Use this analysis to recommend systemic risk limits and circuit breakers for the protocol.