4 Stages of an ICT Liquidity Raid: Do Institutions Really Hunt Your Stops?

Price moves above an old high, trades there briefly, and drops back below it. Or it slips under a previous low, triggers orders around the level, and quickly recovers.

In ICT terminology, this type of move may be called a liquidity raid or liquidity sweep. On social media, the explanation often becomes more dramatic, something like the institutions knew where retail traders had placed their stops and deliberately went after them.

There is a real market mechanism underneath part of that story. Stop orders can cluster, and when triggered together they can add to short-term price movement. But a chart alone cannot tell us who caused a move or prove that somebody deliberately targeted a group of traders.

So, what does an ICT liquidity raid actually describe, and how much of the popular “stop hunt” explanation is supported by market mechanics?

Let’s figure it out!

What Is an ICT Liquidity Raid?

Within ICT and Smart Money Concepts, a liquidity raid generally refers to price moving beyond a previously identified high or low and then reacting around that level.

You may also see similar movements described as liquidity sweeps, liquidity grabs, stop hunts or failed breakouts. These terms are not standardised exchange terminology, and practitioners do not always use them in exactly the same way.

Automated ICT-style indicators, for example, commonly identify raids by testing whether price moves beyond previous swing highs, swing lows or session extremes and subsequently reverses.

Term	Common Trading Usage	What the Chart Can Show
Liquidity raid	Price moves through a suspected liquidity area and reacts	The price movement
Liquidity sweep	Often describes a breach followed by rejection or reclaim	The breach and reaction
Liquidity grab	Often used similarly to raid or sweep	The price movement
Stop hunt	Suggests stops were intentionally targeted	Stops triggering may be inferred, but intent cannot
Breakout	Price crosses a level and sustains movement outside it	The breach and follow-through

The important distinction is between observing price cross a level and claiming to know why it crossed.

What Does Liquidity Mean in ICT Trading?

In market microstructure, liquidity refers broadly to how easily trades can be executed without causing a large price impact. A liquid market can absorb relatively large transactions quickly and with limited effect on price.

ICT uses the word differently. It commonly treats certain visible price areas as places where orders may be concentrated.

What Is Buy-Side Liquidity?

Buy-side liquidity, or BSL, is ICT terminology for expected buy orders above visible highs.

These may potentially include stop orders protecting short positions and buy-stop orders from traders looking for an upside breakout.

What Is Sell-Side Liquidity?

Sell-side liquidity, or SSL, describes expected sell orders below visible lows.

These may include stop orders protecting long positions as well as orders associated with downside breakouts.

ICT practitioners frequently map potential liquidity around swing highs, swing lows, equal highs, equal lows, previous-day extremes and session highs or lows.

The word potential matters. A candlestick chart does not reveal exactly how many stop orders are sitting above an equal high or below a previous low.

Why Can Stop-Loss Orders Matter Around Key Levels?

The idea of price moving into areas where many stop-loss orders may be present is not completely foreign to Indian market surveillance.

In a SEBI order concerning market manipulation, the regulator noted that its Integrated Market Surveillance System had generated alerts including “Stop Loss Fishing.” SEBI described this as a situation where a participant attempts to push the price down to trigger a large number of stop-loss orders for personal benefit. The surveillance alerts related to several BSE-listed securities.

That does not mean every sharp move below a support level or previous low is an example of stop-loss fishing. A surveillance alert is a signal for further examination, not automatic proof of manipulation.

What Happens When Stop-Loss Orders Are Triggered on NSE?

The underlying order mechanism is easier to establish.

NSE states that stop-loss orders remain in a separate Stop-Loss Book until their trigger price is reached or crossed. Once triggered, the order is released into the regular order book.

For example:

• A sell stop-loss order is triggered when the last traded price reaches or falls below its trigger price.
  
  
• A buy stop-loss order is triggered when the last traded price reaches or rises above its trigger price.
  
  

This means that if several stop-loss orders happen to have similar trigger prices, reaching that area can cause multiple orders to become active within a short period.

The exchange rules establish how those orders are activated. They do not tell us how many stop-loss orders are sitting around a particular Nifty high, previous low or round number before they are triggered.

Does This Prove Institutions Hunt Stops in Nifty?

No.

The Indian evidence supports two narrower points:

First, stop-loss orders are activated when specified price levels are reached.

Second, SEBI’s surveillance framework recognises stop-loss fishing as a potential manipulative pattern worth investigating.

But a Nifty candle moving below a previous low and then reversing does not by itself prove that an institution intentionally pushed the market there to trigger retail stops.

To establish manipulation, regulators need evidence from actual orders, trades, participant behaviour and market impact. The shape of the price chart alone is not enough.

What Actually Happens When Your Stop-Loss Is Triggered?

On NSE, the process works in a fairly straightforward way:

• A stop-loss order remains in the Stop-Loss Book until its trigger price is reached or crossed.
  
  
• For a sell stop-loss order, the trigger condition is met when the last traded price reaches or falls below the specified trigger price.
  
  
• For a buy stop-loss order, the trigger condition is met when the last traded price reaches or rises above the specified trigger price.
  
  
• Once the trigger condition is met, the stop-loss order is released into the regular order book for execution.
  
  
• Reaching the trigger price only activates the order. It does not predict what price will do next.
  
  
• After the trigger, price may continue in the same direction, pause, or reverse.
  
  
• This is why a candle moving above an old high or below an old low and then reversing does not automatically prove stop hunting or manipulation.
  
  

Suggested Read: Mean Reversion on Weekly Timeframes: Is Risk-Reward 5x Better Than Intraday Chasing?

How Does an ICT Liquidity Raid Work?

The framework becomes easier to understand when the observable price action is separated from the explanation placed around it.

Stage 1: A Liquidity Reference Forms

A previous swing high, swing low, set of similar highs or lows, or a previous session extreme becomes a visible chart reference.

ICT traders may classify the area beyond that level as potential liquidity.

Stage 2: Price Trades Through the Level

Price moves above the high or below the low.

Within ICT terminology, this breach may be described as taking or raiding liquidity.

At this point, however, the chart only establishes one thing with certainty: the level has been crossed.

Stage 3: Reclaim or Acceptance

What happens after the breach is important.

A reclaim occurs when price crosses a level but moves back into the previous range.

Acceptance describes price remaining beyond the level and continuing to establish activity there.

That difference helps separate a failed breach from a move that develops into continuation.

Stage 4: What Happens After the Raid?

ICT traders may then examine concepts such as displacement, a Market Structure Shift, or Fair Value Gap formation.

These are framework-specific ways of studying the reaction following the breach. They are not guarantees that a reversal will occur.

Suggested Read: 5 Steps to Map Potential Stop Hunts Before They Happen With Order Block + CRT

Buy-Side vs Sell-Side Liquidity Raids

ICT Description	Observable Sequence
Sell-side liquidity raid	Price trades below a previous low, then reclaims it
Buy-side liquidity raid	Price trades above a previous high, then falls back below it

A sell-side raid may therefore be followed by an upward reaction, while a buy-side raid may be followed by a downward reaction.

But the raid itself does not establish what price must do next.

Liquidity Raid vs Breakout: What Is the Difference?

The first part can look almost identical. Both begin with price crossing an established level.

Observation	Raid or Rejection	Breakout or Acceptance
Level is crossed	Yes	Yes
Price quickly returns inside	More consistent	Less consistent
Repeated closes outside level	Less consistent	More consistent
Follow-through	Limited or reversed	Sustained
Previous level reclaimed	Common	Usually not immediately

That creates a problem for anyone trying to label the move in real time.

You normally need additional price information before distinguishing a temporary sweep from sustained acceptance.

One wick beyond a previous high does not automatically make the candle a liquidity raid. Price can breach the same level and continue moving beyond it.

Suggested Read: CRT on 1 Minute Charts: Scalping the Fake Breakout That Catches 90% of Retail Traders

Do Institutions Really Hunt Retail Stop-Losses?

Not necessarily.

Stop-loss orders can cluster around visible price levels, and when many are triggered together, they can add short-term buying or selling pressure.

But a price move through a high or low does not prove that an institution deliberately targeted retail stops.

A chart can show that stops may have been triggered. It cannot show who caused the move or what their intention was.

So the safer conclusion is:

Stop clustering can influence price, but intentional stop hunting cannot be confirmed from a chart alone.

Is Stop-Loss Hunting Market Manipulation in India?

Not necessarily.

Simply moving above a high or below a low and triggering stop-loss orders is not, by itself, evidence of market manipulation.

SEBI’s Prohibition of Fraudulent and Unfair Trade Practices, or PFUTP, Regulations prohibit fraudulent and unfair conduct in the securities market. This includes activity that:

• creates a false or misleading appearance of trading
  
  
• creates artificial demand or supply
  
  
• improperly influences the price of a security
  
  

SEBI lists the PFUTP Regulations as last amended on December 5, 2025.

SEBI’s enforcement history also includes cases involving orders placed without a genuine intention to execute, where such orders were used to create an artificial impression of demand or supply in the order book.

Establishing manipulation therefore requires evidence from orders, trades and participant conduct. The shape of a candlestick or a price move through a previous high or low is not enough on its own.

Can ICT Liquidity Raids Be Detected Algorithmically?

Yes. A computer can be programmed to look for a simple price pattern.

• A possible bearish liquidity raid happens when price moves above a previous high but then closes back below it.
  
  
• A possible bullish liquidity raid happens when price moves below a previous low but then closes back above it.
  
  

The algorithm can also check how far price crossed the level, how quickly it returned, and whether a strong move followed.

The important limitation is that it can detect the pattern on the chart, but it cannot tell whether an institution deliberately caused that move.

How Should a Liquidity-Raid Backtest Be Designed?

A liquidity-raid backtest should follow fixed rules from the start.

1. Define the reference level first: Mark the swing high, swing low, equal high, or equal low using only information available before the breach happens.
   
   
2. Set clear raid rules: Decide how far price must cross the level, how quickly it must return, and what counts as a valid reclaim.
   
   
3. Define displacement clearly: If a strong move after the reclaim is required, set a measurable rule for it instead of judging it visually.
   
   
4. Record every outcome: Include raids that reverse, fail, or continue beyond the level. Do not keep only the successful-looking examples.
   
   
5. Test on unseen data: Apply the same rules to data that was not used to create the strategy.
   
   
6. Watch for common backtesting errors: Avoid look-ahead bias, survivorship bias, overfitting, and repeatedly changing rules until past results look better.
   
   

The goal is to test whether one fixed definition works consistently, not to adjust the rules after seeing what happened.

Bottom Line

Liquidity raids can look dramatic on a chart, especially when price pushes beyond a familiar high or low, triggers stops, and then quickly moves back.

But the chart only shows what happened to price. It does not tell us who caused the move or whether someone deliberately targeted retail traders.

ICT liquidity concepts are useful because they give traders a structured way to study what happens around visible highs, lows, equal levels, and previous session extremes without automatically treating every sharp move as manipulation.

The same thinking applies to algorithmic detection and backtesting. Define the level, define the breach, define the reclaim, and test the same rules across many examples.

That is the more useful way to approach liquidity raids. Focus on what can actually be observed and measured, rather than trying to guess the intention behind every candle.

In the end, the value of liquidity analysis lies in understanding how price behaves around important levels and whether those patterns remain consistent when tested properly.

Disclaimer: This article is for educational and informational purposes only and should not be considered investment or trading advice. ICT liquidity raids, stop hunts, liquidity sweeps, and related concepts are technical-analysis frameworks and do not guarantee future price movements. References to institutional activity or stop-loss behaviour should not be interpreted as proof of manipulation or intent. Market conditions can change rapidly, and historical patterns or backtests may not repeat in live markets. Investors and traders should conduct their own research and consider their risk tolerance before making any market decisions.

FAQs