On 11 November, attackers replaced the homepage of Ukrinform, Ukraine’s state news agency, with the word ‘ZELENET’ and a crossed-out Ukrainian flag. They also renamed its X account and gave it a pro-Russian bio (Kyiv Independent, 11 Nov 2026). The Kyiv Independent places the attack in a series that began on 1 November: the Air Alert app on 1 November, the Kyiv Independent’s own publishing system on 4 November and a fabricated Ukrainska Pravda newsletter on 6 November (Kyiv Independent, 11 Nov 2026). According to one Ukrainian outlet, the account’s @UKRINFORM handle stayed the same, so the hostile profile still looked official (ukrmedia.news, 11 Nov 2026).
Boards approve budgets to protect their data. Few can name who holds the keys to the account that speaks for them in public.
On 11 November, Ukrinform, Ukraine’s state news agency, said hackers had replaced its homepage with the word ‘ZELENET’, a crossed-out Ukrainian flag and a link to a Telegram channel. They also renamed its X account and changed the bio to a pro-Russian slogan (Kyiv Independent, 11 Nov 2026). The agency said it was investigating and restoring services in cooperation with the SBU and the State Service of Special Communications and Information Protection (Kyiv Independent, 11 Nov 2026). Director General Serhii Cherevatyi told Detector Media that suspicious activity was noticed overnight, that the defaced image was removed within minutes, and that this was roughly the fourth similar attack during his tenure (Detector Media, 11 Nov 2026).
We wrote about this pattern two weeks ago, in our ‘Trusted Channel, Hostile Content’ edition. This week we narrow the focus to the part that every organisation has and few govern: the corporate social media account. A website at least sits on infrastructure the organisation runs, patches and monitors. An X account sits on someone else’s platform. Its security usually depends on one password, one recovery email address and whichever staff member set it up years ago. When it falls, the attacker speaks with the organisation’s identity, and here the identity stayed recognisable: according to one outlet, the attackers changed the display name and design but left the @UKRINFORM handle intact (ukrmedia.news, 11 Nov 2026).
Much is still unknown. No source has said how the attackers got into the website or the X account. No actor has been named: Cherevatyi said the type of attack was not yet known and would be established by technical experts (Detector Media, 11 Nov 2026). As of the evening of 11 November, it was not known whether the attackers had reached internal data or editorial systems (ukrmedia.news, 11 Nov 2026). What is on record is the agency’s history. In January 2023, CERT-UA linked a destructive CaddyWiper attack on Ukrinform to Sandworm, which it ties to Russian military intelligence (BleepingComputer, 18 Jan 2023). Cherevatyi says the agency has since installed cyber-defence equipment with US support, and that the adversary now uses AI tools (Detector Media, 11 Nov 2026).
This is a board-level case because the fixes are about ownership before they are about technology. The platform already offers what is needed. X lets an account use a security key as its only second factor (X Help Center, two-factor authentication). It also offers password reset protection, login alerts and a way to revoke third-party apps (X Help Center, account security). UK government guidance asks organisations to keep a register of who has access, reviewed at least monthly, to use role-based recovery contacts and to test a recovery plan (UK Government Security, last updated 14 May 2024). None of that works unless someone is named as the owner of the account. In most organisations, nobody is.
🔎 1. What Happened
1. Ukrinform said on 11 November that hackers had replaced its website’s homepage with the word ‘ZELENET’, an image of a crossed-out Ukrainian flag and a link to a Telegram channel (Kyiv Independent, 11 Nov 2026).
2. The same day, the agency’s X account was renamed ‘ZELENET’ and its bio was changed to a pro-Russian slogan (Kyiv Independent, 11 Nov 2026). One outlet reports that the account’s @UKRINFORM handle was not changed, which it says could make the posts look official (ukrmedia.news, 11 Nov 2026).
3. Director General Serhii Cherevatyi said suspicious activity was noticed overnight, the agency was in contact with specialist services by morning, and the defaced image was removed within minutes (Detector Media, 11 Nov 2026).
4. The website then showed a maintenance notice while specialists worked on restoring it (ukrmedia.news, 11 Nov 2026).
5. Ukrinform said it was working with the State Service of Special Communications and Information Protection and the SBU to establish what happened, assess the consequences and restore normal operation (Kyiv Independent, 11 Nov 2026; Detector Media, 11 Nov 2026).
6. Cherevatyi said this was roughly the fourth similar attack during his tenure. He said a previous one was stronger and took the site offline for several hours, and that the adversary uses AI tools (Detector Media, 11 Nov 2026).
7. No source has disclosed how the website or the X account was accessed. No actor has been attributed (Detector Media, 11 Nov 2026; ukrmedia.news, 11 Nov 2026).
8. This is not the first attack on the agency. In January 2023, CERT-UA linked a destructive attack on Ukrinform, which used the CaddyWiper malware launched through Windows Group Policy, to the Sandworm group (BleepingComputer, 18 Jan 2023).
📊 2. Business Impact
Confirmed: The organisation lost control of its public voice. For a period, the state news agency’s homepage and its X profile both displayed hostile messaging under the agency’s own name (Kyiv Independent, 11 Nov 2026).
Confirmed: The website was unavailable. After the defacement was removed, the site showed a maintenance notice while restoration continued (ukrmedia.news, 11 Nov 2026). How long it was down and when the X account was fully recovered: not publicly disclosed.
Confirmed: Staff time was diverted to incident response. The agency was working with the SBU and the State Service of Special Communications and Information Protection on investigation and restoration (Kyiv Independent, 11 Nov 2026).
Assessment: Reputational and information-integrity damage. A recognisable handle carrying a hostile name and bio lends the attacker the agency’s credibility (ukrmedia.news, 11 Nov 2026, notes the posts could look official). How many people saw the hijacked profile: scale not publicly disclosed. This is SEG’s assessment.
Assessment: Possible deeper compromise. As of the evening of 11 November, it was not known whether the attackers had reached internal data or editorial systems (ukrmedia.news, 11 Nov 2026). Until that is answered, the incident cannot be treated as a surface defacement only.
Assessment: Repeat targeting. Cherevatyi describes roughly four similar attacks during his tenure (Detector Media, 11 Nov 2026), and CERT-UA linked a 2023 wiper attack on the agency to Sandworm (BleepingComputer, 18 Jan 2023). Ukrinform should be treated as a persistent target. This is SEG’s assessment.
🧩 3. Likely Root Cause
An unauthorised party gained enough control of the X account to change its display name, bio and profile imagery.
Source: Kyiv Independent, 11 Nov 2026; ukrmedia.news, 11 Nov 2026. The access method has not been disclosed: a stolen password, a hijacked session, a compromised recovery email, a connected third-party app or a compromised staff device are all possible. Changing a profile without changing the handle suggests session- or credential-level access rather than an account transfer. That is SEG’s assessment, not a confirmed finding.
An unauthorised party could change what the website served on its homepage.
Source: Kyiv Independent, 11 Nov 2026; Detector Media, 11 Nov 2026 (the site’s defences were breached after suspicious activity overnight). Whether this came through CMS credentials, a CMS or plugin vulnerability, hosting or CDN access has not been disclosed.
Both of the agency’s main public channels were changed in the same attack, which suggests either a shared weakness (credentials, a staff device or a shared email account) or a coordinated attack on two separate accounts.
Assessed from the simultaneous website and X changes reported by Kyiv Independent, 11 Nov 2026. No source links the two technically.
The organisational social account is governed like a consumer account. X’s own security guidance is written for individual users and does not cover organisational ownership, delegated access or offboarding.
Assessed from X Help Center, account security and compromised-account pages (no organisational controls described). Ukrinform’s own account governance is not public. This is a sector-wide assessment, not a finding about Ukrinform.
⚠️ 4. Control Failures
[CF-1] IDENTITY: Authentication on the organisation’s X account did not stop an unauthorised party from changing its name, bio and imagery. The account was not protected by a phishing-resistant factor that an attacker could not reuse.
[CF-2] TECHNOLOGY: The website’s publishing path, whether CMS, hosting or CDN, let an unauthorised party replace the homepage. No integrity control stopped or immediately reverted the change.
[CF-3] PROCESS: There was no visible, rehearsed playbook for ‘our public channel is speaking for someone else’. That means a named owner, a platform escalation path, a pre-written correction and an out-of-band channel for confirming it.
[CF-4] THIRD PARTY: The organisation’s public identity depends on a platform whose recovery process is built for individuals: reset by email, then a support ticket (X Help Center, compromised-account page). Recovery contacts, connected apps and platform escalation were not managed as supplier-risk items.
[CF-5] PEOPLE: The staff who run social and web channels are the access path. Shared passwords, personal recovery emails, publishing from personal devices and slow offboarding are the habits attackers exploit, and they are rarely covered by training.
🛡️ 5. Recommendations
5A — Organisational & Technical Controls
Audience: security and IT teams.
CF-1: Lock every organisational social account with a security key as the only second factor (ISO/IEC 27001:2022 Annex A 8.5 — secure authentication; CIS Controls v8.1 Safeguard 6.3, IG1; NIST SP 800-63B phishing-resistant authenticators)
On X, enrol at least two FIDO2 security keys per organisational account (one in daily use, one sealed in the safe) and then remove SMS and authenticator-app methods. X states that a security key can be used as the sole authentication method (X Help Center, two-factor authentication). Turn on Password reset protection under Settings > Account > Security, so a reset needs the account’s registered email or phone (X Help Center, account security). Keep the login and email-change alerts on, and route them to a monitored shared mailbox, not one person’s inbox. Store the password only in the corporate password manager or PAM vault, with check-out logging, so publishers use the account without ever seeing the password. Where a scheduling tool needs access, connect it through OAuth, never with the password. Temporary passwords for apps that need one expire after one hour (X Help Center, two-factor authentication), so do not issue standing ones. Run the same baseline on every other platform the organisation uses: Facebook, Instagram, LinkedIn, YouTube, Telegram and TikTok.
CF-1 / CF-4: Make the recovery path as strong as the login (ISO/IEC 27001:2022 Annex A 5.17 — authentication information, A 5.23 — information security for use of cloud services; UK Government Security, Using social media securely)
Re-register every organisational account to a role-based recovery address (for example socialmedia-owner@ on the corporate domain), never a person’s own mailbox. UK government guidance says recovery contacts must be role-based, not personal (UK Government Security, last updated 14 May 2024). Protect that mailbox with FIDO2-only sign-in and a Conditional Access policy that blocks forwarding rules and unmanaged devices. A recovery mailbox with weaker MFA than the account is the real front door. Remove personal phone numbers from accounts. Each quarter, open the Applications tab and revoke any connected app without a named business owner (X Help Center, account security).
CF-2: Make the homepage impossible to change quietly (ISO/IEC 27001:2022 Annex A 8.9 — configuration management, A 8.32 — change management; CIS Controls v8.1 Safeguard 6.5, IG1)
Put the CMS admin interface behind SSO with FIDO2, plus a ZTNA gateway or IP allow-list, so it is not reachable from the open internet. Disable local CMS accounts and XML-RPC or legacy API logins. Give editors a role that can publish articles but not change templates, the homepage layout or plugins. Template and plugin changes go through a separate change-managed admin role. Run file-integrity monitoring on theme, template and plugin directories, and a synthetic check every five minutes that hashes the rendered homepage and pages the on-call engineer when it differs from the expected structure. Keep a static ‘known-good’ homepage on the CDN that can be switched in with one action while the CMS is investigated.
CF-3: Write and rehearse a ‘hijacked voice’ runbook (ISO/IEC 27001:2022 Annex A 5.24 — incident management planning, A 5.26 — response to information security incidents; NIST SP 800-61 Rev. 3)
Name one accountable owner and one deputy per channel in a register reviewed at least monthly (UK Government Security, last updated 14 May 2024). The runbook covers the first hour. Revoke sessions, rotate the password from the vault, revoke connected apps, lock the recovery mailbox, and file a support request with the platform from the account’s registered email, including the username and the date of last known access (X Help Center, compromised-account page). Prepare the correction in advance: ‘Our account was compromised. Posts since [time] are not ours.’ Publish it from a second verified channel (website, Telegram or another platform) within 30 minutes. Hold a 60-minute tabletop exercise twice a year in which communications, IT and legal recover a test account end to end. Preserve evidence (screenshots, platform notification emails, CMS logs) before restoring, so attribution is not lost in the clean-up.
CF-5: Treat channel operators as privileged users (NIS2 Art. 21(2)(i) — human resources security, access control and asset management; CIS Controls v8.1 Safeguard 6.2, IG1 — establish an access revoking process)
Keep a register of everyone who can publish to each channel. Remove access the day someone changes role or leaves, and rotate any password they could see the same day. UK guidance says passwords should be changed ‘immediately’ (UK Government Security, last updated 14 May 2024). Allow publishing only from managed, compliant corporate devices, which UK government guidance also requires of staff (UK Government Security, last updated 14 May 2024). Give any social-media management or scheduling tool the same FIDO2 and access-review controls as the platform accounts it can post to. Deliver the rules below (5B) as a standing briefing for communications, marketing, editorial and executive-assistant staff.
5B — For the People Who Run Your Organisation’s Social Media and Website
CF-5: NIS2 Art. 21(2)(g) — basic cyber hygiene and cybersecurity training; ISO/IEC 27001:2022 Annex A 6.3 — information security awareness, education and training
1. Never share the account password, and never keep it in a document or chat.
Use the company’s password tool, which lets you post without seeing the password. If a password has been in an email, a spreadsheet or a chat message, assume someone else can find it, and ask IT to change it.
2. Sign in with the security key, not a text-message code.
A small hardware key that you plug in or tap is the one sign-in method a fake login page cannot steal. Text-message codes can be intercepted or phished.
3. Treat any message from ‘platform support’ about your account as suspicious.
Attackers send fake warnings about copyright strikes, verification or suspension to get you to a fake login page. Go to the platform yourself, by typing the address, and never type a code or approve a sign-in you did not start.
4. If the account posts or changes something you did not do, call the named owner straight away.
Minutes matter. Do not wait to be sure or try to fix it yourself. Take screenshots, then call. The team has a plan for this, and it starts with your call.
5. Post only from your work laptop or phone, and tell IT the day your role changes.
A personal device or a forgotten login on an old phone is the easiest way in. When you move teams or leave, your access should leave with you the same day.
SEG Security Awareness Training — free to forward inside your organisation
⚖️ 6. Regulatory Relevance
Law of Ukraine No. 2163-VIII — ‘On the Basic Principles of Ensuring Cybersecurity of Ukraine’
National cybersecurity framework for state bodies and critical-infrastructure entities; roles of the SSSCIP, CERT-UA and the SBU in incident response.
Ukrinform is a state news agency, and its response ran through the SSSCIP and the SBU (Kyiv Independent, 11 Nov 2026). This is the framework under which its incident handling, and any reporting obligation, falls. The specific provisions applicable to this incident have not been established in this analysis.
NIS2 — Directive (EU) 2022/2555 (EU parallel)
Art. 21(2)(i) human resources security, access control policies and asset management; Art. 21(2)(j) multi-factor authentication; Art. 21(2)(d) supply-chain security; Art. 21(2)(g) cyber hygiene and training; Art. 23 (24 h early warning / 72 h notification)
Ukraine is not bound by NIS2, but the same attack on an EU public-administration body in scope (Annex I, public administration) would engage it directly. Organisational social accounts are network and information systems used to deliver the entity’s service to the public, so access control (21(2)(i)) and MFA (21(2)(j)) apply to them as much as to internal systems. Dependence on the platform is a supplier relationship under 21(2)(d). A hijack that misleads the public could meet the Art. 23 significant-incident threshold where it causes severe disruption or reputational harm. That is a per-case test under national transposition. Scope note: news media are not a NIS2 sector, so a private newsroom is generally out of scope, while a state body that publishes is in scope by being public administration.
ISO/IEC 27001:2022
Annex A 5.16 identity management; 5.17 authentication information; 5.18 access rights; 5.23 information security for use of cloud services; 5.24 and 5.26 incident management planning and response; 8.5 secure authentication; 8.9 configuration management
A 5.23 is the clause that brings social platforms into the ISMS. It requires the organisation to define how it acquires, uses, manages and exits cloud services, and a social account is one. In practice, few statements of applicability list social accounts as assets at all. Adding them to the asset inventory, with an owner under A 5.9, is the first audit fix.
CIS Controls v8.1
Safeguard 5.1 — establish and maintain an inventory of accounts (IG1); 6.2 — establish an access revoking process (IG1); 6.3 — require MFA for externally-exposed applications (IG1); 6.5 — require MFA for administrative access (IG1)
Every safeguard that maps to this case is IG1, the baseline expected of every organisation regardless of size. A social account with no inventory entry, no offboarding step and SMS-only MFA is an ownership gap, not a capability gap. That puts it on the board’s agenda, not the engineers’.
NIST SP 800-63B — Digital Identity Guidelines: Authentication and Lifecycle Management
Authenticator assurance levels; phishing-resistant authenticators (cryptographic, verifier-bound, e.g. FIDO2/WebAuthn) as the strong-assurance option
This gives a vendor-neutral standard for a requirement such as ‘security key only’ on organisational accounts, and a reason to reject SMS codes and authenticator-app codes for high-impact publishing identities: both can be relayed through a fake login page.
🤝 7. How SEG Can Help
CF-1 / CF-4: SaaS Configuration Review
SEG inventories every organisational social, publishing and newsletter account. For each one we check the second-factor method, password reset protection, recovery email and phone, connected apps and alert routing. You get a per-account remediation list ending with ‘security key only, role-based recovery, no orphan apps’.
CF-2: Penetration Testing
SEG attacks your web publishing path the way an outsider would: the CMS login and admin exposure, plugin and template vulnerabilities, hosting and CDN control panels. We also test whether a homepage change would be detected and reverted within minutes.
CF-3: vCISO
SEG’s vCISO assigns a named owner to every public channel, writes the ‘hijacked voice’ runbook and the pre-approved correction messages, and runs the twice-yearly recovery tabletop exercise with communications, IT and legal. Board reporting on channel ownership becomes a standing item.
CF-4: Third-Party Risk Assessment
SEG treats your platforms and social-media management tools as suppliers: what recovery and escalation routes exist, what access the scheduling tool holds, and what happens to your identity if the vendor is compromised.
CF-5: Security Awareness Training
SEG turns the 5B rules into a 20-minute module for communications, marketing and editorial staff. We follow it with a simulated ‘platform support’ phishing exercise aimed at the people who hold publishing access.
🎯 Strategic Signal
Four trusted Ukrainian channels in eleven days shows a deliberate tactic, not chance. Hostile actors are going after the organisation’s voice rather than its data, because a hijacked official account turns the victim’s credibility into the attacker’s message. For European organisations, social accounts are now part of the attack surface that board risk registers rarely list. Expect regulators and insurers to start asking who owns them.
💬 SEG Expert View — Dmytro Yershov, CISO
“When we sit with a board, we ask a simple question: who owns your X account? The answers are revealing. Marketing says IT. IT says communications. Communications names an agency that set it up years ago, or an employee who has since left. That account speaks for the organisation to every citizen, journalist and partner, and in a crisis it is the first place people look. Yet it rarely appears on the risk register, it is rarely in the asset inventory, and it is often protected by a text-message code sent to one person’s personal phone. What happened to Ukrinform is not a story about sophisticated tooling. We do not yet know how the attackers got in. It is a story about which assets an organisation decides are worth governing. Our advice to every executive team is to treat public channels as tier-0 identities. Give each one a named owner and a deputy, a security key, a role-based recovery address and a rehearsed recovery plan, and report their status to the board every quarter, as you would for your payment systems. The cost is small. The cost of your own voice telling the public something you never said is not.”
— Dmytro Yershov, CISO, SEG (Security Expert Group)
📚 Sources
• Kyiv Independent — Hackers target Ukraine’s state news agency Ukrinform, replace website with anti-Ukrainian messages — November 11, 2026
• Detector Media — Хакери з ночі атакують ресурси Укрінформу (Hackers have been attacking Ukrinform’s resources since the night; interview with Director General Serhii Cherevatyi) — November 11, 2026
• ukrmedia.news — Хакери зламали «Укрінформ»: що сталося із сайтом і X (Hackers breached Ukrinform: what happened to the website and X) — November 11, 2026
• BleepingComputer — Ukraine links data-wiping attack on news agency to Russian hackers (2023 CaddyWiper incident, CERT-UA attribution) — January 18, 2023
• X Help Center — How to use two-factor authentication — accessed November 15, 2026 (no date shown)
• X Help Center — About account security — accessed November 15, 2026 (no date shown)
• X Help Center — Help with my compromised account — accessed November 15, 2026 (no date shown)
• UK Government Security (Government Cyber Unit) — Using social media securely — last updated May 14, 2024
✉️ Need help securing your organisation?













