DC Guardsman Shooting: Google Searches for CIA-Linked Afghan Spiked HOURS Before Attack

In the most explosive development since yesterday’s shooting near the White House, alleged attacker Rahmanullah Lakanwal — a former member of a CIA-backed Afghan strike force — appears to have had his name searched multiple times inside Washington, D.C. in the hours before the ambush took place.

The pattern mirrors the infamous pre-event search anomalies observed before the Charlie Kirk assassination attempt, where key individuals were searched in D.C. and Israel ahead of the attack. The question now hanging over the capital: How did Washington insiders know this man’s name before the public even knew an attack was coming?

What is already confirmed by U.S. media is that Lakanwal had previously served as part of a CIA-partnered militia in Kandahar, a paramilitary “strike force” that U.S. intelligence worked alongside during the Afghan war. His status as a vetted U.S. intelligence asset is not speculation — it has been acknowledged publicly by officials and cited across multiple outlets.

And yet, despite that background, the 29-year-old reportedly drove across the country and, at approximately 2:15 p.m., opened fire on two unarmed West Virginia National Guard soldiers patrolling near the Farragut West station.

But the timeline is what has shaken even mainstream observers. Screenshots alleging Google Trends spikes for “Rahmanullah Lakanwal” in Washington, D.C. at 2:24 a.m., 3:28 a.m., and again around 8 a.m. — long before the shooting — have ignited speculation that someone was monitoring his status or anticipating an operation.

Newsweek has already acknowledged the growing controversy over these Trend anomalies as conspiracy discussions surge across social media. Though of course they are framing them as “conspiracy theories” rather than legitimate investigation.

This pre-attack search activity suggests something far more troubling than a lone, radicalized gunman. Someone — or multiple someones — may have been checking whether a known CIA-linked asset had carried out a mission.

That possibility alone demands forensic scrutiny: IP subpoenas, timestamp verification, and a full audit of who searched this man’s name and why.

Because Lakanwal was not an unknown figure drifting anonymously through America. He was a former paramilitary operative with a file, a sponsor, and an intelligence-community history. The agencies involved in his evacuation and vetting know exactly who he is — and who he stayed in contact with.

Taken together — the pre-event searches, the intelligence background, the location of the attack, and the lack of any publicly known motive — the narrative being presented to the public looks increasingly incomplete.

The American people are being told this was a random act of violence. But the digital footprint suggests coordination. The resettlement records imply oversight. And the operational style — a daylight ambush on uniformed personnel near the White House — looks less like a spontaneous breakdown and more like a message.

Until federal investigators release the full vetting file, communication logs, and IP data linked to those early-morning searches, the most important question remains unanswered:

Who was Rahmanullah Lakanwal working for on the day he pulled the trigger — and who knew before the first shot was fired?