Description

Market Manipulation covers the post-launch use of market-mechanism surfaces — price-discovery, order-books, oracle windows, liquidation cascades, cross-venue spreads — to extract value from other market participants or from the protocol's own market-mediated accounting. The defining shape is that no contract bug is required: the protocol behaves as designed, the venues quote prices honestly, the oracle reads its inputs correctly. The exploit lives at the market-mechanism layer — the attacker shapes price discovery, book state, or window timing into a configuration that the design admits as legitimate but that produces an unintended distribution of value.

T17 is intentionally distinct from T3 (Holder Capture). T3 sub-Techniques T3.002 (Wash-Trade Volume Inflation), T3.003 (Pump-and-Dump Coordination), and T3.004 (Influencer-Amplified Promotion-and-Dump) cover launch-time / early-lifecycle concentration of holder state and the listing-/ volume-credibility primitives that depend on it. T17 cross-references those sub-Techniques because the wash / pump / promote-and-dump primitives are also load-bearing inside post-launch market-manipulation kill-chains — the same wash-trade pattern that fakes a launch's liquidity is the pattern that fakes mid-life listing-eligibility, and the same pump-and-dump shape that fires at TGE fires again on illiquid mid-cap altcoins after CEX listings. T3 mappings on the existing sub-Techniques are preserved; T17 is added as an additional parent for the post-launch market-manipulation framing.

T17 is intentionally distinct from T5 (Value Extraction). T5 covers direct on-chain value-egress patterns — treasury sweep (T5.005), exit-scam liquidity removal (T5.001), router / approval drainer (T5.002), permit-signature drain (T5.003), sandwich / MEV (T5.004), vesting-cliff dump (T5.006). T17 is market-distortion-mediated extraction: the value flows because price discovery, order-book state, or window timing was shaped into a configuration that the protocol's accounting then settled against. T5.004 (Sandwich / MEV Extraction) is a boundary case because MEV extraction is itself a market-manipulation primitive at the per-block / per-transaction level — T5.004 is dual-mapped under T5 (the on-chain extraction framing) and T17 (the market-manipulation framing) without rename.

T17 is intentionally distinct from T9 (Smart-Contract Exploit). T9.001 (Oracle Price Manipulation) and T9.006 / T9.006.001-004 (Subjective-Oracle Resolution Manipulation) sub-Techniques cover the code-mechanism failure modes where the oracle / resolution surface is the load-bearing exploitable contract surface. T17 is the market-mechanism framing of the same incident class: the oracle behaved as specified, but the attacker shaped market state into a configuration that the oracle reported faithfully and the protocol accounted against. T9.001 / T9.006.x mappings on existing worked examples are preserved; T17 is added as an additional parent for the post-launch market-manipulation framing of these incidents.

T17 is intentionally distinct from T16 (Governance / Voting Manipulation). T16's load-bearing surface is voting power converted into a protocol decision. T17's load-bearing surface is price / order-book / oracle-window state converted into a market-mediated value flow. The kill-chains can compose — Mango Markets October 2022 reads as T9.001 (oracle manipulation as the code-mechanism layer) → T17 / T17.x (market-manipulation framing as the cross-cutting Tactic) → T16.002 (hostile-vote treasury drain) → T5.005 (treasury egress) — but the Tactic boundaries partition cleanly by which surface the attacker is acting on at each step.

T17 sits in the kill-chain in parallel with T5 (both are realisation-phase Tactics) and after T9 / T3 / T16 when those Tactics are upstream conditions. The Tactic boundary is the layer at which the load-bearing surface is market-mechanism state — price discovery, order-book state, oracle-window selection, cross-venue spread, liquidation-cascade dynamics. If the attack converts market-mechanism state into a value flow, it is T17; if the attack converts a code bug into a value flow, it is T9; if the attack converts voting power into a protocol decision, it is T16; if the attack pulls value directly via a routing / approval / treasury primitive, it is T5.

What defenders observe

Cross-venue price-discovery distortion (T17.001): correlated price moves across CEX / DEX venues whose spread closes inside an arbitrage window opened by a primary attack on one venue; victim cohorts on the lagging venue settle against the distorted reference price; cohort-attribution typically locates a single cluster of arbitrage bots routing across the spread.
Liquidation-cascade engineering (T17.002): predatory liquidation bots positioned at the edge of the liquidation-eligibility threshold; cascade ignition correlated with thin-liquidity windows (low-volume hours, cross-venue depeg events, oracle-update windows); harvest accrues to the bot operator at distressed prices that are not available to the broader market.
Order-book spoofing (T17.003): large limit orders posted on DEX / perp order-books that are cancelled in the last seconds before fill; the order-book state during the spoof window misleads other participants into adverse fills; spoof-and-cancel pattern visible in the per-order-event trace but not in the executed-trades trace.
TWAP / window manipulation (T17.004): trading volume concentrated inside the TWAP window of a downstream contract (DAO treasury swap, vesting unlock, oracle-update) rather than uniformly over time; the TWAP window's price is then used as a settlement reference in a contract whose math allows the manipulator to extract value at the manipulated rate.
Wash-trade-credibility cohorts (T17 ↔ T3.002): post-launch wash-trade volume to maintain CEX-listing eligibility, exchange-incentive farming, or analytics-platform ranking; the cohort attribution is funder-graph clustering at the wash-trader account level.
Pump-and-dump coordination cohorts (T17 ↔ T3.003 / T3.004): Telegram-channel-coordinated or influencer-amplified post-launch pump-and-dump events; OAK does not classify Telegram-cohort PnD as launch-time-only; the same pattern fires repeatedly on illiquid mid-cap altcoins through a token's lifetime.
Sandwich / MEV (T17 ↔ T5.004): per-block MEV extraction that is itself a market-manipulation primitive against the victim swap; T5.004's existing observed-indicator set carries over.
Oracle-mediated market manipulation (T17 ↔ T9.001 / T9.006.x): the existing T9.001 and T9.006.x defender signal sets carry over; T17 frames the same incidents at the market-manipulation Tactic level rather than at the oracle-code-mechanism Tactic level.

Relationship to other tactics

T17 is the cross-cutting Tactic that gives unified Tactic-level visibility to market-manipulation patterns that v0.1 OAK had distributed across T3 (launch-time wash / pump), T5 (sandwich-MEV at the on-chain extraction layer), and T9 (oracle / subjective-oracle manipulation at the code-mechanism layer). The shape of the kill-chains that T17 makes legible:

T3.002 (Wash-Trade Volume Inflation) ↔ T17. Wash-trading is a market-manipulation primitive that is load-bearing both at TGE (T3 launch-time framing) and post-launch (T17 framing — listing-eligibility maintenance, exchange-incentive farming, analytics-platform ranking, mid-cap altcoin liquidity-illusion). Both parents preserved.
T3.003 (Pump-and-Dump Coordination) ↔ T17. Telegram-coordinated PnD is the canonical micro-scale market-manipulation primitive. T3 frames it at the holder-capture / launch layer; T17 frames it at the cross-cutting market-manipulation Tactic. Both parents preserved.
T3.004 (Influencer-Amplified Promotion-and-Dump) ↔ T17. Influencer-amplified PnD adds an off-chain entry-vector (T15.005-adjacent) and a public-market amplification primitive that scales the PnD beyond the Telegram-cohort baseline. Same dual-parent reasoning as T3.003.
T5.004 (Sandwich / MEV Extraction) ↔ T17. Sandwich-MEV is itself a market-manipulation primitive at the per-block level. T5 frames it as on-chain value extraction; T17 frames it as the per-block / per-transaction case of market manipulation. Both parents preserved.
T9.001 (Oracle Price Manipulation) ↔ T17. T9.001 is the code-mechanism framing — the oracle is the load-bearing exploitable surface. T17 frames the same incidents at the market-manipulation layer — the attacker shaped market state into a configuration that the oracle reported faithfully. Mango Markets October 2022, BonqDAO February 2023, Cream October 2021 are all dual-parented under both T9 and T17 once the cross-reference lands.
T9.006 / T9.006.001-004 (Subjective-Oracle Resolution Manipulation cluster) ↔ T17. Polymarket-class subjective-oracle manipulation (DVM vote capture, resolution-spec ambiguity, off-chain source coercion, operational insider trading) is a market-manipulation primitive against the prediction-market layer. T9 frames it at the code-mechanism layer (the UMA DVM is the load-bearing contract surface); T17 frames it at the market-manipulation layer (the market for the prediction-market token is what the manipulation distorts).

The new T17.001-004 sub-Techniques cover market-manipulation patterns that do not have an existing parent at T3 / T5 / T9 / T16:

T17.001 — Cross-venue arbitrage-driven price-discovery distortion. Multi-venue spread exploitation that produces market-wide price-discovery distortion as the attack outcome (distinct from T5.004 sandwich-MEV which extracts within a single block, and distinct from T9.001 which manipulates the oracle's input venue).
T17.002 — Liquidation-cascade engineering. Predatory bots that intentionally trigger liquidation cascades to harvest at distressed prices (distinct from T9.001 which manipulates the price-feed at the oracle layer; T17.002 is the use of oracle volatility / thin liquidity to engineer cascading liquidations as the harvest mechanism).
T17.003 — Spoofing / cancel-flood order-book manipulation. DEX limit-order books and perpetuals order books manipulated via spoof orders + last-second cancellation (distinct from T3.002 wash-trade which produces fake executed volume; T17.003 produces fake resting-order state without execution).
T17.004 — TWAP / time-window manipulation against DAO treasury / vesting math. Manipulating TWAP windows or vesting-cliff timing to extract favourable rates against the downstream contract's settlement math (distinct from T9.001 generic oracle manipulation and from T5.006 vesting-cliff dump).

T17 mitigation is concentrated at the venue-design layer (deeper liquidity, multi-venue oracle quorum, randomised TWAP-window selection, spoof-detection and order-book-quality monitoring at venue level), the protocol-design layer (settlement against multi-venue references rather than against single-venue prices, liquidation-throttling and per-block caps to bound cascade harvest, vesting / treasury-swap math that is robust to TWAP-window concentration), and the market-surveillance layer (cohort-attribution applied to wash-traders, predatory-liquidation-bot operators, spoof-and-cancel patterns; CTI integration on publicly-known PnD coordination channels). The dollar-loss-prevented metric for T17 is most sensitive to venue-side liquidity depth and oracle architecture — a protocol whose price reference has multi-venue redundancy and TWAP-window-randomisation defeats T17.001 / T17.004 by construction; a venue with deep order-book liquidity and venue-side spoof-detection defeats T17.003.

Sub-Techniques (new under T17)

OAK-T17.001 — Cross-Venue Arbitrage-Driven Price-Discovery Distortion
OAK-T17.002 — Liquidation-Cascade Engineering
OAK-T17.003 — Spoofing / Cancel-Flood Order-Book Manipulation
OAK-T17.004 — TWAP / Time-Window Manipulation Against DAO Treasury / Vesting Math

Cross-referenced sub-Techniques (existing under T3 / T5 / T9; T17 added as additional parent)

OAK-T3.002 — Wash-Trade Volume Inflation
OAK-T3.003 — Pump-and-Dump Coordination
OAK-T3.004 — Influencer-Amplified Promotion-and-Dump
OAK-T5.004 — Sandwich / MEV Extraction
OAK-T9.001 — Oracle Price Manipulation
OAK-T9.006 — Subjective-Oracle Resolution Manipulation
OAK-T9.006.001 — DVM Vote Capture
OAK-T9.006.002 — Resolution-Spec Ambiguity Exploitation
OAK-T9.006.003 — Off-Chain Resolution-Source Coercion
OAK-T9.006.004 — Operational Insider Trading

No existing parent-Tactic mapping is removed. T17 is added as an additional parent on each of the cross-referenced sub-Techniques.

Discussion

The core editorial question this Tactic answers: why introduce T17 as a cross-cutting Tactic that re-parents existing T3 / T5 / T9 sub-Techniques rather than a single-parent Tactic with its own non-overlapping sub-Techniques?

The answer is structural. v0.1 OAK distributed market-manipulation patterns across three Tactics by contextual phase (T3 = launch-time, T5 = on-chain extraction, T9 = code-mechanism), which kept each individual Technique page coherent against its Tactic's primary framing but made the cross-cutting market-manipulation pattern invisible at Tactic-level. A defender asking "what does the OAK corpus say about market manipulation?" at v0.3 had to look in three different Tactics and reconstruct the cross-cutting class manually. A defender asking "is this pattern wash-trading or pump-and-dump or sandwich-MEV or oracle manipulation?" had to pick one Tactic per case rather than acknowledge that several mid-life market-manipulation incidents legitimately span multiple Tactics simultaneously (a wash-trade cohort that becomes a pump-and-dump that ends with sandwich-MEV against the dumping wallet's victims is a single operational behaviour with a single attacker cluster).

T17 makes the cross-cutting class legible without renaming any existing OAK ID. The existing T3.002 / T3.003 / T3.004 / T5.004 / T9.001 / T9.006.x sub-Technique pages remain in place at their primary Tactic homes; T17 is added as an additional parent on each. This is a schema-minor additive change per VERSIONING.md: downstream consumers pinned to v0.3 continue to resolve every existing ID under its existing primary Tactic; consumers consuming v0.4-and-later see the additional T17 parent edge.

The 4 new T17.x sub-Techniques cover market-manipulation patterns that v0.1 OAK did not have a Technique-level home for at all:

T17.001 (cross-venue arbitrage-driven price-discovery distortion). v0.1 OAK had T5.004 (sandwich-MEV, single-block / single-venue) and T9.001 (oracle manipulation against a single feed). Neither covered the multi-venue case where the manipulation is legitimate cross-venue arbitrage but the consequence is market-wide price-discovery distortion that produces a victim cohort on the lagging venue. The T17.001 surface is real (cross-venue spread arbitrage is a continuous phenomenon in crypto markets) but the canonical worked-example anchor at extraction-scale is editorially weaker than the T17.002 / T17.003 / T17.004 anchors; T17.001 is introduced as draft with the gap honestly documented.
T17.002 (liquidation-cascade engineering). Distinct from T9.001 oracle manipulation: T9.001 covers the oracle-side manipulation that drives the price-feed; T17.002 covers the attacker-side liquidation-bot operation that harvests at distressed prices. Multi-event cohort: 2022-06 stETH cascade, 2022-05 Terra / UST cascade, 2024-04 ezETH cascade, 2025-07 Lido stETH / Aave queue-saturation cascade, plus per-protocol predatory-liquidation-bot reports across Aave / Compound / Maker / Liquity. Maturity at introduction: emerging, anchored against the existing depeg-cascade worked examples and the broader predatory-liquidation-bot literature.
T17.003 (spoofing / cancel-flood order-book manipulation). Order-book DEXes (dYdX, Hyperliquid, GMX V2 perps, Drift) are operationally young; the canonical extraction-scale anchor for spoof-and-cancel against a crypto order-book is editorially weaker than the long-running CEX spoofing literature (CFTC enforcement against Sarao, Coinbase wash-trade cases). T17.003 is introduced at draft maturity with the gap honestly documented.
T17.004 (TWAP / time-window manipulation against DAO treasury / vesting math). Distinct from T9.001 generic oracle manipulation: T17.004's load-bearing surface is the downstream contract's TWAP window used as a settlement reference for treasury swap, vesting-unlock, or oracle-update math — not the oracle's input venue. v0.1 OAK has the class boundary against T9.001 but lacks a canonical extraction-scale anchor; introduced at draft maturity with the gap honestly documented.

T17 is purely additive against T3 / T5 / T9 / T16. The existing sub-Technique pages remain in place; every T17 cross-referenced sub-Technique carries both its existing primary Tactic AND the new T17 parent edge. Downstream consumers pinned to v0.3 continue to resolve the existing IDs without breakage; consumers consuming v0.4-and-later see the additional T17 cross-cutting Tactic.

Maturity boundary at introduction: T17.002 is emerging (anchored against existing depeg-cascade worked examples and broader predatory-liquidation-bot cohort literature). T17.001 / T17.003 / T17.004 are draft (the class is real and operationally documented but the canonical extraction-scale anchor at the dollar-loss scale of the existing T16.001-003 / T9.001 / T5.004 anchors has not yet landed in the OAK corpus). Future contributors should anchor each draft sub-Technique once a public-record case lands at extraction-scale; promotion to emerging requires at least one canonical worked example.

Maintainer notes

T17 is the OAK editorial response to the v0.3 TAXONOMY-AUDIT observation that market-manipulation patterns were the largest single un-Tactic'd cross-cutting cohort in the corpus. T3.002 / T3.003 / T3.004 / T5.004 / T9.001 / T9.006.x collectively span ~$300M+ in realised loss across multiple distinct operational sub-patterns that the v0.3 schema could only enumerate as primary-parented sub-Techniques inside their respective Tactic homes. Adding T17 as a cross-cutting Tactic with cross-references-not-renames makes the cross-cutting class legible at Tactic-level without breaking the existing schema.

Per VERSIONING.md, adding T17 is an additive schema change (schema-minor bump, 0.3 → 0.4): existing T1-T16 IDs are unchanged, and existing T3.002 / T3.003 / T3.004 / T5.004 / T9.001 / T9.006.x parent-Tactic mappings are preserved. Anchor worked examples carry both the existing primary Tactic mapping AND the new T17 cross-reference, so downstream consumers pinned to the v0.3 schema continue to resolve the existing IDs without breakage.

Future T17 contributions should preserve four boundary rules:

Market-mechanism state is the load-bearing surface. If the attack does not go through a price / order-book / window / cross-venue-spread primitive, it is not T17. Code-bug exploitation is T9; voting-power-against-protocol is T16; direct treasury / approval / routing pulls are T5; launch-time holder-state concentration is T3.
No contract bug required. T17's load-bearing distinction from T9 is that the protocol behaves as designed. If the exploit requires a code defect (reentrancy, missing access check, integer overflow), it is T9.
Existing primary Tactic mappings preserved. Every T3.002 / T3.003 / T3.004 / T5.004 / T9.001 / T9.006.x worked example keeps its existing T3 / T5 / T9 mapping. T17 is added; existing Tactic mappings are never removed in favour of T17.
Cross-cutting Tactic, not replacement. T17 is parent-to-many; the cross-referenced sub-Techniques retain their primary Tactic identity. T17 sub-Techniques (T17.001-004) are sub-Techniques of T17 only and do not parent to T3 / T5 / T9 unless a future schema-major bump migrates them.

OAK-T17 — Market Manipulation