Ketan Parekh Front-Running Case: SEBI’s 2025 Interim Order Explained
Front-running converts confidential order information into a trading advantage before a large client’s transaction reaches the market. It attacks both client trust and market fairness.
Current position
On 2 January 2025, SEBI issued an interim order-cum-show-cause notice involving Rohit Salgaocar, Ketan Parekh and other noticees. It recorded prima facie conclusions, directed impounding of approximately ₹65.77 crore of alleged unlawful gains and imposed interim restrictions. The noticees were entitled to respond; the interim record should not be described as a final adjudication.
Key facts at a glance
| Order date | 2 January 2025 |
|---|---|
| Nature | Interim order-cum-show-cause notice |
| Amount | Approximately ₹65.77 crore directed to be impounded |
| Legal status | Prima facie observations pending further process |
What this means in practice
What front-running means
A person trades ahead of a substantial impending client order using non-public information, seeking to benefit from the price impact of that order.
Why communication evidence matters
Trade timing alone may be ambiguous. Regulators examine messages, device records, relationships, fund flows, order sequences and profit patterns together.
Why institutions need information barriers
Asset managers and brokers should limit access to large-order information, monitor employee and connected-account trading, and review unusual pre-trade patterns.
Practical example
A dealer learns that a large institutional client will sell a stock and sends the information to a connected trader, who sells first and buys back after the client order moves the price. The gain comes from information entrusted for execution.
A practical decision framework
1. Define the exact claim
Identify the entity, product, transaction, period and legal forum. Do not apply a headline about one company, order or market event to a different fact pattern.
2. Reconcile the economics
Trace the claim to cash flow, balance-sheet exposure, contractual rights and the measurement definition. Separate revenue from transaction value, profit from liquidity and allegation from final outcome.
3. Check the operative record
Read the latest primary document and note whether it is a policy paper, interim order, final order, judgment, agreement, filing or historical report.
4. Convert the lesson into a control
Assign an owner, deadline, evidence requirement and escalation threshold. A lesson is useful only when it changes a decision or control.
Action checklist
- Restrict large-order data to need-to-know users.
- Monitor employee, dealer and connected-account trading.
- Use time-sequenced alerts around large client orders.
- Review messaging and device controls under lawful policy.
- Escalate repeated matching patterns to compliance.
Evidence and document checklist
- SEBI orders and subsequent proceedings
- Order-management audit trail
- Call, message and access logs
- Employee and connected-account declarations
- Fund-flow and profit analysis
Common mistakes and red flags
Common mistakes
- Treating a show-cause notice as guilt
- Looking only at trade timing without communication or relationship evidence
- Failing to map connected entities
- Allowing traders to use personal channels for client orders
Red flags
- Trades repeatedly precede the same client
- Multiple accounts share devices, funding or contacts
- Large orders are discussed outside approved systems
- Surveillance alerts close without documented investigation
Escalation route
For regulated products or proceedings, start with the responsible entity’s grievance or compliance channel and preserve written records. Use the relevant regulator, exchange, court or tribunal process where applicable. Obtain specialist advice before a limitation period, filing deadline, tax position or material right is affected.