By Douglas J. Hagmann
This weekend, my neighbor asked me what I knew about the murder of Seth Rich. Instead of answering him, I asked him what he knew about it, which admittedly was not much. He only heard about it from a drive-by media report and couldn’t understand why a shooting during an “attempted robbery” almost a year ago in Washington, DC was being discussed.
It was then I realized that not everyone, even those seemingly knowledgeable about current events, understands the potential significance of this incident. It was then I decided to write this most basic report intended for those who are just learning of the murder of Seth Rich, and explain why it is of such importance.
I also hope to convey why there is such opposition to the investigation and discussion of this tragic event, and why there is such vitriol levied against anyone who is searching for answers to what many want to dismiss as a “botched robbery.”
The following is a very basic introduction of the case compiled from limited releases by official sources, my personal interviews with investigative journalists on my radio show, the Hagmann Report and my own investigation. First, here are the most basic facts.
Victim: Seth Conrad Rich
Address: 2113 1st St.
Washington, DC 20001
Age: 27 DOB: 1/3/1989
Prior Address: 1222 Euclid, Washington DC 20009
Employer: Democratic National Committee (DNC)
Position: Data Analyst
Parents: Joel & Mary Rich, Farnam St, Omaha, NE (Douglas County)
Date of Crime: 10 July 2016 Time: 0419 hours
Location of crime: Southwest corner of W Street & Flagler Place NW, Washington, DC
Incident Type: GSW (Gunshot Wound(s)) – The victim was reportedly shot twice in the back with a small caliber handgun.
Metropolitan Police Public Incident Report (CCN #16113797; Issued 10 July 2016 at 0710):
“CIC reports the sound of gunshots at 2134 Flagler Pl. NW. Upon arriving to the scene, the decedent was laying in the Southwest corner of the intersection of W St. and Flagler Pl. NW. The decedent was conscious and breathing with apparent gunshot wound(s) to the back. The decedent was transported to local area hospital and was pronounced dead by attending physician at 0557 hours.”
The public incident report listed the following [capitals/punctuation in source document]:
Responding officer: Jody O’Leary (#7859) – MPD. Assisting officer: ROBERT WINGATE ROBINSON (#7634) (Body Worn Camera), Derek Tarr (#9237) (Other Officers At Scene): Shea Ellis (#9499) (Other Officers At Scene), Benjamin Velez (#6631) (Body Worn Camera), Mark Lee (#6141) (Body Worn Camera).
The motive for the shooting, according to subsequent statements by or on behalf of the Metropolitan Police Department or the Rich family, was that the shooting was a “botched robbery” attempt. This despite that nothing was reportedly taken from the victim. The victim also reportedly sustained pre-mortem wounds to his face, hands and knees in what was described as defensive wounds.
Also according to reports, the victim was conscious upon the arrival of police, although he allegedly provided a previous address to authorities. It is unclear whether the responding officers, as is customary in a shooting, asked the victim who shot him or a description of the shooters. No BOLO alerts were sent out as a result of the initial contact with police.
The preceding information concludes the public information either provided by or admitted to by public officials. Numerous important factors and relationships have been left out by police and public officials.
Mr. Rich reportedly sustained two gunshot wounds from a small caliber handgun. One wound was alleged to be a “through and through” wound, while the other bullet reportedly struck his liver. He was transported to an unidentified hospital where he allegedly died a few hours later.
His murder might have gone as just another statistic and testament to the violence that plagues our inner cities, except for nagging questions about the activities of Seth Rich prior to his murder, combined with other oddities that involve departure from standard operating procedure by the MPD.
On March 17, 2017, GOP lobbyist Jack Burkman announced the creation of the Profile Project and announced a $105,000 reward for information leading to the conviction of the Rich murder. As reported by investigative journalist Liz Crokin, Burkman is now claiming that the MPD is thwarting his efforts through non-cooperation.
While other people and groups have added to the reward that now totals well over a quarter of a million dollars, conspicuously absent is his own employer – the DNC.
In the face of accusations of departure from police department SOP and other oddities, the Rich family spokesman, Brad Bauman, has been vitriolic in his condemnation of anyone asking questions about the murder of Seth Rich.
Family spokesman Brad Bauman happens to be a Public Relations crisis manager with the Pastorum Group in Washington, D.C., a firm with progressive ties. In his role as a communications consultant, Bauman offers “strategic communications advice to Democratic candidates and labor unions,” according to his public profile page on LinkedIn.
The real problems with this case, however, have yet to be addressed.
In the matter of the murder of Seth Conrad Rich, the core issue exists in the growing body of evidence that strongly indicates that Mr. Rich, though his position as a data analyst at the DNC during a hotly contested primary election, might have discovered fraudulent and perhaps criminal activity that could affect the outcome of the party nomination (from Bernie Sanders to Hillary Rodham Clinton).
Subsequent reports verified that Seth Rich was an ardent supporter of then-DNC candidate Bernie Sanders. By virtue of his job description, Rich was positioned to have access to data that could prove poll tampering in favor of Clinton. Concurrently, his importance to anyone conspiring to maintain the specific narrative of foreign interference rose exponentially, if not unexpectedly, should his alleged discovery be exposed. Should such alleged tampering be made public, it would obviously have devastating consequences to those “fixing” the polls.
Accordingly, Mr. Rich might well have found himself in a very lonely and unenviable position of possessing information which, at the very least, is vital to the integrity of our election process. Specifically, this information would be most problematic for those conspiring to assure the party nomination of Hillary Rodham Clinton in the Democratic primaries.
This situation is further clouded and exacerbated by constant media allegations of “hacks” of our election process by foreign entities, specifically the Russians, which has become and continues to be the official account of the DNC and supporters of Hillary Clinton. While these alleged hacks reportedly both pre-date and postdate the murder of Seth Rich, he has nonetheless become a key subject of interest due to his position with the Democratic National Committee and the outcome of the 2016 Presidential election.
It is important to note that on June 14, 2016, about a month before Seth Rich was murdered, The Washington Post reported that “Russian hackers” obtained DNC communications, and reportedly had access to DNC computers for approximately one year before discovery and lockdown. It is also vital to note that this information did not come from the FBI or any law enforcement agency of the United States government, but from the private cyber security firm CrowdStrike, which was called in to handle the DNC breach despite the FBI offering its services which were curiously rejected.
These odd rejections were verified by former FBI Director James Comey himself during his testimony before the Senate Intelligence Committee on January 10, 2017. Comey testified that the FBI made multiple requests, but was denied direct access to the Democratic National Committee’s email servers and other “hacked devices” as part of its probe of Russian hacking.
It was within this environment of alleged poll fixing and reports of Russian intrusion into the DNC computers that Seth Rich found himself. Having direct access to the DNC computers and perhaps finding irregularities that could impact the outcome of the primaries, it is conceivable that Seth Rich might have been long on critical information but short on trusted friends.
Anyone who has spent any time in Washington knows that trust within the beltway is a rare commodity. Consider then, the predicament of a young man from Nebraska at the moment he realizes that he possesses evidence of fraudulent and criminal activity at the highest levels of the DNC.
For the last decade, Wikileaks has existed and received millions of leaked documents that exposed, among many things, the machinations of the powerful and those in power. The methods used to provide information to Wikileaks have consisted of electronic transfer as well as the transfer of information through handoffs of portable storage devices.
Is it possible that Seth Rich reached out to Wikileaks to expose the possible and alleged fraud within the DNC?
According to published reports by at least two sources, the answer is yes. One source is Rod Wheeler, the DC private investigator hired by a representative of the Rich family to investigate his murder. Another is the infamous hacker Kim-Dot-Com. One might also consider Julian Assange of Wikileaks himself, although not directly, but by his offering a $25,000 reward on August 9, 2016, less than one month after Seth Rich was murdered.
Considered in totality, there appears to be sufficient circumstantial evidence to suggest that Seth Rich did, in fact, communicate with Wikileaks at some point prior to his murder. Direct evidence in the form of forensic analysis of his computer devices and cell phones, however is presently non-existent. Why? There appears to be a problem locating his electronic devices, as both the DC police and the FBI deny custody.
The primary component that is used to cast doubt on the legitimacy of the election of Donald Trump is foreign interference of our election process, specifically by Russia. To this day, this unproven conspiracy theory is repeated ad nauseum by the corporate media without any authenticated proof from any government law enforcement agency.
The primary source of this narrative is the private cyber security firm CrowdStrike as referenced by the June 14, 2016 report in The Washington Post and picked up by other media outlets. CrowdStrike was hired and paid for by the DNC in June 2016, essentially making the Russian hacking account a paid product of the DNC.
All told, there were at least four-(4) separate hacks into the DNC computers: the Democratic Caucus “hack(s),” the Podesta email “hack(s),” the DNC “hack(s)” and the Clinton Foundation “hack(s).” Included in the above is the strange account of the Awan brothers, three highly-paid Pakistani nationals who were employed as IT specialists shared among House Democrats. Working under Debbie Wasserman-Schultz, the Awan brothers are at the center of controversy in a series of thefts discovered early this year.
Also overlapping this period was the FBI investigation into the handling of classified emails by Hillary Rodham Clinton and staff. On July 5, 2016, FBI Director James Comey held a press conference at the conclusion of his investigation, where he accused Clinton of serious mishandling of classified information contained in emails and computer documents, but stopped short of recommending any referrals to the Department of Justice.
As one can see, there exist numerous problems with computer security, both party data and government equipment and information. The Seth Rich case, however, surrounds the DNC polling data that might have given the party’s nomination to Hillary Clinton rather than Bernie Sanders.
The importance of exposing the information possessed by Seth Rich is two-fold and very significant. Obviously, it would expose the false Russian hacking narrative that has been used to delegitimize the Presidency of Donald Trump, and also expose the “rigging” of the DNC nomination process.
There is more – much more – about this. There is much more information that will break this week about this case. For now, however, I am going to print this explanation for my neighbor, who is a hostage of the corporate media.
Perhaps this will help your neighbor when the murder of Seth Rich arises in conversation in the coming days. And I suspect it will.
By Douglas J. Hagmann
Most people know that we’ve been lied to about the attacks in Benghazi, but few realize the extent of those lies or the hidden secrets they cover. After all, the lie is different at every level. Thanks to a well placed source with extensive knowledge about the attack, the disturbing truth is slowly beginning to emerge and is lining up with information contained in my previous articles published here weeks ago (Here, Here and Here). The truth reveals the most serious situation in the world today as it involves the interests and destinies of us all.
According to the U.S. government, Ambassador Christopher Stevens and three other Americans were killed during a spontaneous protest at the consulate office in Benghazi by a frenzied crowd of Muslims outraged over an obscure internet video. Recently released “sensitive but not classified e-mails” from Stevens to the U.S. Department of State painted a picture of poor security for U.S. personnel and the embassy, which was obviously true but had little to do with the events of September 11, 2012. The failure to dispatch an extraction team or otherwise rescue the men during a firefight that lasted upwards of nine grueling and tortuous hours was not the result of any intelligence failure, but caused by our unwillingness to widen the conflict and expose the nature and scale of our true mission in Benghazi.
Based on information provided by my source and corroborated elsewhere, the official account by administration officials is a mosaic of lies that were necessary to cover the unpalatable truth of covert actions taking place in Libya, Syria, Turkey, Jordan and Lebanon. The primary objective of our covert actions was to secretly arm anti-Assad “rebels” in Syria by funneling arms from Libya to Syria via Turkey, with other destinations that included Jordan and Lebanon. Regarding the threat to Stevens and the other murdered Americans, the truth will reformat the persistent question posed to government officials, from UN Ambassador Susan Rice to White House Spokesman Jay Carney and others from “how could you not have known” to “how could you have done these things?”
First, it is important to understand that Ambassador Stevens, Sean Smith, Glen Dougherty and Tyrone Woods were not killed at a consulate office in Benghazi—as there is not such office there. They died at one of the largest CIA operations centers in the Middle East, which was located in Benghazi and served as the logistics headquarters for arms and weapons being shipped out of the post-Qaddafi Libya.
Although the U.S. government insisted that Stevens was involved in securing and destroying the numerous caches of arms and weapons once under the control of Qaddafi, the operation was more complex than that. The visual accounts of weapons being destroyed were indeed real, but those weapons were not operational. The working weapons were actually separated and transported to holding facilities for their eventual use in Syria. Russia was fully aware of this operation and warned the U.S. not to engage in the destabilization of Syria, as doing so would endanger their national security interests. Deposing Assad, as despotic as he might be, and replacing him with a Muslim Brotherhood-led regime would likely lead to unrestrained Islamic chaos across the region.
According to my source, Ambassador Stevens was in Benghazi on September 11, 2012 to meet with his Turkish counterpart, who reportedly warned Stevens that the operation was compromised. They met in person so that Stevens could be shown overhead satellite images, taken by the Russians, of nefarious activities taking place in Turkey. But just what were these nefarious activities?
It is reasonable to suspect that these activities were more dire than just your average “gun running” operation. Since the overthrow of Qaddafi, it is estimated that upwards of 40 million tons of weapons and arms were shipped out of Libya to Syria. But it was also known inside intelligence circles that Qaddafi possessed chemical weapons in addition to numerous surface-to-air missiles. Could it be that Russia obtained unmistakable surveillance footage of the anti-Assad “rebels” being shown how to load chemical payloads onto missiles inside Turkey near the border of Syria? Weapons, of course, that were shipped from Libya by the CIA in conjunction with various Muslim Brotherhood rebel groups. If so, such weapons could be used as a “false flag” type of operation—one that would be implemented to “set-up” Assad by making it appear that he was using these weapons on forces dedicated to his overthrow.
The blowback by the international community would be swift and punishing, and the entirety of the civilized world would be demanding his overthrow. NATO would then be used to expedite his ouster, and Russia’s moral position within the international community would be weakened. Was the meeting held to show Stevens that the operation was compromised and that they had to stop?
While the administration asserts that the attack in Benghazi was conducted by a group of rebels acting alone, the facts seem to indicate otherwise. The level of coordination was such that we did not deploy military assets, located just an hour or two away by air, to rescue Stevens and the others at the CIA operations center in their time of need. If, as the administration contends, that the attack was perpetuated by a group of frenzied rebels, our military could have easily handled them in short order. So why was there no rescue operation?
Perhaps the statements made yesterday by Leon Panetta, U.S. Secretary of Defense provides some insight if one analyzes the essence of those statements. Among other things, Panetta said that “…the basic principle is that you don’t deploy forces into harm’s way without knowing what’s going on…” Well, it has been confirmed we did know what was taking place on the ground in Benghazi, so exactly what did Panetta mean by this statement?
Against the backdrop of the official story, it makes little sense. If, however, one considers the alternative, that the attack was coordinated and was a nation/state sponsored attack, then it becomes clearer. Panetta and the highest levels of this administration likely knew exactly what we were doing, and knew that the operation was compromised. They knew, or had reason to believe, that the attack was being conducted at a nation/state level in response to our covert operation in Libya and arming the anti-Assad Syrian opposition.
Although Russia figures prominently here, Iran now comes into focus as Russia is not likely to directly engage U.S. forces. They must, however, protect their interests. Much like we were using anti-Assad forces to advance our objectives in Syria, Russia was using Iranian-backed forces to protect theirs. It appears that the attacks were conducted or facilitated by Iranian assets—perhaps as many as three teams of assets in Benghazi.
As the White House and other agencies monitored intelligence in real-time, they faced a dilemma. They knew that the nation/state sponsored attack teams were lying in wait for U.S. rescue forces to arrive, which is the reason the fight did not conclusively end sooner. They did not know exactly where all of the attack teams were, but knew they were present based on signal communication intercepts. Could they risk such exposure by deploying a rescue team to Benghazi, only to end up with another Black Hawk down type scenario? In addition to that scenario, the entire operation now becomes exposed for what it is. Take another look at Panetta’s statement in that context. Does it now make more sense? Bad PR in an election year, no?
As daylight approached with no response from the U.S. and no aid to the Americans under fire, the attack teams had to disperse into the cover of the remaining darkness, but not before their mission was accomplished. And sadly, it was.
From the day of attack in Benghazi, Iran has been engaged in a full spectrum attack on the U.S. and NATO across the board involving embassies, bombing and even cyber attacks. All of this is the fallout from the arms and weapons smuggling operation, which was far greater than understood by the Western media.
Russia has now moved their contingent of S-400 missiles into much of Syria in anticipation of NATO establishing an “air cap” over Syria. A ten-mile “buffer zone” along Syria’s border has been created for Syrian refugees, but it also acts as a catalyst for the encroachment into Syrian territory. It sets the stage for further advancement and erosion of Syrian land, incrementally, of course.
It is also of critical importance to note that last weekend, Russia completed large-scale exercises of their Strategic Nuclear Forces under the watchful command of President Vladimir Putin. These were the first such nuclear exercises conducted since the fall of the Soviet Union.
To those with discernment, it is obvious that we are at the precipice of World War III. Putin himself stated as much, noting that WW III will not start in Iran but Syria, his own “red line in the sand.”