Stay up to date with notifications from The Independent

Notifications can be managed in browser preferences.

Ministerial aide sacked after warning against leaking was leaked

Chief whip used ‘canary trap’ sting in bid to find source of information passed to media

Andrew Woodcock
Political Editor
Friday 18 December 2020 16:31 GMT
Comments
Andrew Lewer says, ‘In nearly 20 years of elected office I have never leaked to the press’
Andrew Lewer says, ‘In nearly 20 years of elected office I have never leaked to the press’ (Chris McAndrew / UK Parliament)

Your support helps us to tell the story

This election is still a dead heat, according to most polls. In a fight with such wafer-thin margins, we need reporters on the ground talking to the people Trump and Harris are courting. Your support allows us to keep sending journalists to the story.

The Independent is trusted by 27 million Americans from across the entire political spectrum every month. Unlike many other quality news outlets, we choose not to lock you out of our reporting and analysis with paywalls. But quality journalism must still be paid for.

Help us keep bring these critical stories to light. Your support makes all the difference.

A ministerial aide has been sacked after Boris Johnson’s chief whip conducted a sting designed to catch out leakers.

Andrew Lewer was sacked from his junior government role as parliamentary private secretary in the Home Office after a letter calling for an end of leaks to the press was itself leaked to the Guido Fawkes website of Westminster scandal and gossip.

It is understood that chief whip Mark Spencer used slightly different wording in each copy of the letter, in order to allow officials to identify the source of any information which found its way into the media.

Lewer, PPS to the policing minister Kit Malthouse, is believed to have denied he had leaked the letter when confronted by Conservative whips.

And the Northampton South MP told the Politico website: “In nearly 20 years of elected office I have never leaked to the press.”

Mr Spencer’s letter, addressed sent to all PPSs and vice-chairs of the Conservative Party, was sent out on 14 December.

Three days later, it appeared on the Guido Fawkes website under the headline: “Leaked: Chief Whip writes to PPSs warning them not to leak.”

As well as quoting from the warning, the website published a picture of the letter itself, making it clear which version had been passed on.

The letter said that there had been “a lack of clarity” over what was expected from PPSs and vice-chairs in relation to their responsibilities under the ministerial code.

It pointed out that prime minister Boris Johnson’s foreword to the code “strictly prohibits ‘leaking’ or any other breaches of trust”.

And it warned: “I would like to take this opportunity to remind you of the severe consequences that you will face, should you choose to breach the code.”

Any violation of the code will lead to removal from their position “with immediate effect” and no mitigating arguments will be accepted, it warned.

Mr Johnson’s former adviser Dominic Cummings had vowed to wage war on leakers during his year in No 10, but was never able to stem the flow of awkward information to the media.

Most embarrassingly, news of the impending second lockdown in England was leaked shortly after it was agreed at a top-level meeting, forcing the PM to bring his announcement forward. A Cabinet Office inquiry continues into the “chatty rat” responsible.

No 10 briefed last month that it was ready to use a “canary trap” strategy to find the source of leaks by disseminating information in a format that would identify those passing it on.

At the time, the tactic drew mockery that it would not work if potential leakers were told it would happen.

Mr Lewer did not immediately respond to a request from The Independent for comment.

Join our commenting forum

Join thought-provoking conversations, follow other Independent readers and see their replies

Comments

Thank you for registering

Please refresh the page or navigate to another page on the site to be automatically logged inPlease refresh your browser to be logged in