![photo afp photo afp](https://i.tribune.com.pk/media/images/Shakib-al-Hasan1723127331-0/Shakib-al-Hasan1723127331-0.jpeg)
On the fifth day of the first Test against Pakistan at Rawalpindi Cricket Stadium, Bangladesh all-rounder Shakib Al Hasan lost his composure.
The incident unfolded during the 33rd over of Pakistan's second innings when Shakib, visibly frustrated, directed his anger at Mohammad Rizwan, who was batting with Abdullah Shafique.
Rizwan was taking an unusually long time to settle at the crease, disrupting Shakib’s rhythm. In response, Shakib threw the ball toward Rizwan, leaving the umpire visibly shocked.
Shakib Al Hasan, known for his on-field confrontations, added another incident to his record during the match. However, he soon realized his mistake and offered an apology to the umpire, who responded with a stern expression.
Meanwhile, Bangladesh captain Najmul Hossain Shanto approached the umpire to express concerns over Rizwan's time-wasting, but the umpire appeared largely indifferent to the complaint.
Meanwhile, Bangladesh Cricket Board (BCB) President Faruque Ahmed announced on Saturday that a decision about Shakib Al Hasan's future will be made after the ongoing Test against Pakistan.
Shakib was implicated in a murder case filed on Thursday, August 22, by Rafiqul Islam, the father of Rubel, a garment factory worker who was killed on August 5 in Dhaka's Adabor area.
In response to these grave allegations, Supreme Court lawyer Shajib Mahmood Alam sent a legal notice to the BCB on Saturday, representing Advocate Md Rafinur Rahman.
The notice demands Shakib's immediate suspension from all forms of cricket, citing that his involvement in a criminal case disqualifies him from continuing in the national team according to International Cricket Council (ICC) regulations. The notice, as obtained by Cricbuzz, underscores the necessity of his removal in light of the serious charges against him.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ