Breaking: Tory Twitter account hacked

happygeek 1 562 Views

The Twitter account of the Conservative MP for Suffolk Coastal, Therese Coffey, has been well and truly hacked it would appear. According to "The attackers bombarded social media users with sexually explicit messages and comments after gaining access to her Blog, Facebook and Twitter account details".

Although the Facebook account would seem to be back under Tory control, with a message apologising that her account had been hacked and stating that she has the email address "of the person who has hacked in" which will enable her to "do something about it" the Twitter account would appear to still be awaiting a clean up after the hacker, calling himself thegh0st, posted a handful of offensive anti-Tory tweets.

The last warned another Twitter user, Tim Montgomerie who is editor of ConservativeHome blog, that "youre next on the chopping list...freak" and other postings included one which stated "David Camerons wifes a slut...she dresses like a whore!!!"

Dani AI

Generated

This thread describes a clear account compromise of a high‑profile social feed. The priority after discovery is fast containment and evidence preservation so the owner (or their team) can regain control and investigators can learn how it happened.

Immediate containment checklist:

  • Use a known‑good device and network. From there, change the account password to a strong, unique one and enable two‑factor authentication (prefer hardware/FIDO2 keys if available).
  • If still logged in anywhere, revoke all active sessions and remove suspicious third‑party app access. Check and secure the linked email account (reset its password, remove unknown forwarding rules, and confirm recovery options).
  • Preserve proof before mass deletion: take dated screenshots, export the account archive if the platform allows it, and note message IDs/URLs. Do not amplify the offending posts.

Organizational and legal steps:

  • Treat political or public‑figure compromises as incidents: notify the platform through the official “compromised account” route, document timelines, and consider contacting law enforcement if there are threats or extortion.
  • Prepare a short, factual public statement from an authenticated channel (website or other verified accounts) once the account is under control; avoid speculative or emotional language.

Prevention and hardening:

  • Enforce unique passwords and mandatory 2FA for all staff with account access; prefer hardware security keys for high‑risk accounts.
  • Limit admin rights, audit access regularly, use enterprise SSO where possible, and keep a tested incident response playbook with contact points for platform support and legal/PR.
  • Train staff to recognise phishing and never reuse credentials across services.

This expands on ’s report by focusing on practical next steps and prevention. Third parties should not retweet or engage with suspected hacked content — report it instead so it stops spreading.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.

Edit Preview