Insider reveals likely players behind the Guardian’s ‘fake’ Assange-Manafort story

Fidel Narvaez
Support us and go ad-free

In an extensive interview, a former Ecuadorian diplomat says he assumes that intelligence contractors were a source of the smear which claimed former Trump campaign manager Paul Manafort had visited WikiLeaks founder Julian Assange.

This follows an exclusive Canary article in which the same diplomat called the Guardian story “fake”, explaining why visits by Manafort could not have taken place. WikiLeaks, the Intercept‘s Glenn Greenwald, the Courage Foundation, and others outlets all shared or referenced this article.

Intelligence sources

Following the Canary article, the Washington Post admitted that the Guardian‘s report had relied:

on unnamed sources and an “internal document” written by Ecuador’s intelligence agency.

Now, in an interview with The Real News, former Ecuadorian consul and first secretary Fidel Narváez has suggested that the intelligence firm contracted to provide security to the Ecuadorian embassy in London was likely involved in the ‘fake’ story regarding Manafort’s ‘visits’:

Meanwhile, Ecuadorian president Lenín Moreno has made it clear he doesn’t want Assange to remain in the embassy in London much longer.

Read on...

The article’s third author

The Guardian article was written by regulars Luke Harding and Dan Collyns, as well as Ecuadorian journalist and former anti-government activist Fernando Villavicencio. All three names appeared in the print version of the story. But in the online version, Villavicencio’s name mysteriously disappeared:

And here are the three journalists in Quito, shortly before the publication of the article:

Villavicencio also boasted of his collaboration shortly after the article’s release:

Repeat offender?

But as Narváez also claimed, Villavicencio was the “major” player in the ‘fake’ Assange-Manafort story.

Villavicencio writes regularly about Assange on his blog. And he’s hardly a newcomer to the Guardian. One Ecuadorian media report previously accused him in 2014 of altering an official document which he supplied to the newspaper. This archived Ecuadorian Embassy web page provides further details of what happened, naming Villavicencio as the fabricator. The document’s metadata apparently showed the wrong date and Villavicencio as the author.

The Guardian has questions to answer

Award-winning independent journalist Glenn Greenwald has since published a series of questions to the Guardian (which also reference the Canary interview with Narváez):

But so far, there appears to have been no response:

The Canary will be interested in the Guardian‘s response to these questions. We have also put to the newspaper further questions about its sources in the Manafort article, and the reliability of the document it refers to. It had not responded by the time of publication.

Featured image via screenshot

We know everyone is suffering under the Tories - but the Canary is a vital weapon in our fight back, and we need your support

The Canary Workers’ Co-op knows life is hard. The Tories are waging a class war against us we’re all having to fight. But like trade unions and community organising, truly independent working-class media is a vital weapon in our armoury.

The Canary doesn’t have the budget of the corporate media. In fact, our income is over 1,000 times less than the Guardian’s. What we do have is a radical agenda that disrupts power and amplifies marginalised communities. But we can only do this with our readers’ support.

So please, help us continue to spread messages of resistance and hope. Even the smallest donation would mean the world to us.

Support us
  • Show Comments
    1. Fake news? Luke Harding? The Guardian? Well, I never!

      Perhaps one day they’ll explain where that ‘convoy of Russian tanks’ they described ‘rolling over the Ukrainian border’ ever went? The photo o a lone tank 1000’s of kilometres away in the Urals, snapped 3 years earlier, barely cuts the mustard, Kath VIner.

    Leave a Reply

    Join the conversation

    Please read our comment moderation policy here.