A viral moment in PSL 2026 saw Sahibzada Farhan deny Steve Smith a single, sparking comparisons with a past BBL incident involving Babar Azam.
The ongoing Pakistan Super League 2026 has delivered several gripping moments, with Steve Smith making headlines during his debut stint in Pakistan. Representing Multan Sultans, the Australian star has played a key role in helping the team climb to the top of the points table after five matches.
Smith’s presence has added experience and stability to the Sultans’ batting lineup, as the team continues to dominate the early phase of the tournament.
Farhan Denies Single, Sparks Viral Moment
An unusual on-field moment involving Smith and teammate Sahibzada Farhan grabbed attention during a clash against Quetta Gladiators. The incident occurred on the final ball of an over when Smith attempted to retain strike by taking a single.
However, Farhan refused the run, leaving the Australian visibly surprised. Smith had been looking to keep the strike heading into the next over after contributing to a brisk start, but the decision from Farhan halted that plan. The clip quickly circulated online, becoming a talking point among fans and analysts.
BBL Incident with Babar Azam
The situation reminded many cricket followers of a similar episode in the Big Bash League earlier in 2026. During a match for the Sydney Sixers, Smith had famously declined a single to Babar Azam during the ‘Power Surge’ phase to retain strike.
ALSO READ | WATCH | Steve Smith Denies Single To Babar Azam, Smashes Record Over In BBL Clash
In that instance, Babar was seen visibly frustrated after being denied the opportunity to face the next delivery. The parallel between the two incidents has not gone unnoticed, with fans highlighting the irony of Smith finding himself on the receiving end this time around.
The moment has added another layer of intrigue to PSL 2026, showcasing how small on-field decisions can quickly become viral talking points in modern cricket.
This article follows WicketWatcher’s editorial standards. Learn more in our Editorial Policy or report an issue via our Corrections Policy.