Lil Durk accused of placing bounties on six people including quando rondo according to court documents
Court documents reveal a witness accused Lil Durk of ordering hits on six individuals after King Von’s 2020 death

Chicago rapper Lil Durk, born Durk Banks, has been accused by a confidential witness of placing bounties on multiple individuals, including rapper Quando Rondo, according to newly filed court documents reviewed by XXL Magazine.
In a response filed by prosecutors on Monday (Oct. 27) to a defense motion seeking to suppress certain evidence, the government cited information from a confidential informant (identified as CW-1) who alleged that Durk ordered attacks on several people following the death of his associate King Von in November 2020.
“The affidavit further disclosed that CW-1 knew that defendant Banks placed other monetary bounties for the murder of people with whom defendant Banks was feuding, including six other individuals,” the filing states. The same document references corroborating evidence linking Durk to the killing of Saviay’a Robinson, Quando Rondo’s cousin, who was fatally shot in 2022.
Prosecutors claim Durk financed a group of five men to travel to California to target Quando Rondo in retaliation for King Von’s death. However, during the attempted hit, Robinson was allegedly killed instead. Durk has consistently maintained his innocence regarding the murder-for-hire accusations.
In a development viewed as favorable for the defense, the prosecution confirmed that federal investigators had reviewed Durk’s social media and iCloud accounts but decided not to use any of that material in the upcoming trial.
Durk is currently facing murder-for-hire charges and has pleaded not guilty. His trial is set to begin on January 6, 2026, in federal court.
Neither Durk’s legal team nor federal prosecutors have issued further public comments regarding the newly unsealed affidavit.


















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