In a report released on February 15, 2026, Google's Threat Intelligence group has attributed a new wave of cyber attacks against organizations in Ukraine to a suspected Russian nation-state actor. The campaign is notable for deploying a previously unseen malware framework that Google has named CANFAIL. The attacks appear to target high-value sectors, including defense and energy, consistent with espionage and disruption objectives related to the ongoing geopolitical conflict. The rapid emergence of novel malware like CANFAIL and VoidLink underscores the inadequacy of signature-based antivirus and reinforces the critical need for advanced, behavior-based threat detection and response capabilities.
This campaign represents a continuation of cyber operations linked to the conflict between Russia and Ukraine. The use of a new, custom malware framework like CANFAIL indicates that the threat actor is a sophisticated, well-resourced group, likely a state-sponsored entity. Developing novel malware is a way for such groups to evade existing security solutions that rely on known signatures or indicators of compromise (IOCs).
While technical details of the CANFAIL malware are sparse in the source material, its emergence alongside other new families like VoidLink points to a key trend: threat actors are engaged in a continuous development cycle, creating bespoke tools for specific campaigns. This agility requires defenders to shift their focus from reacting to known threats to proactively hunting for unknown malicious behaviors.
Threat Actor: While not named, Google's attribution to a "suspected Russian nation-state actor" points towards established groups known to operate in the region, such as APT28 (Fancy Bear) or APT29 (Cozy Bear), though this is speculation without further data.
Targets: The campaign is focused on Ukrainian organizations, with a specific emphasis on the defense and energy sectors, which are critical infrastructure and high-value intelligence targets.
Without specific details on CANFAIL, we can infer the likely TTPs based on similar nation-state campaigns targeting Ukraine:
T1566 - Phishing.T1204 - User Execution.T1053 - Scheduled Task/Job) or a new service (T1543 - Create or Modify System Process).T1071 - Application Layer Protocol.T1041 - Exfiltration Over C2 Channel) for espionage purposes or preparing for disruptive attacks on critical infrastructure.The impact of this campaign is primarily strategic and geopolitical. For the targeted Ukrainian organizations, a successful breach could lead to:
For the broader cybersecurity community, this serves as a reminder that geopolitically motivated cyber attacks are a major driver of malware innovation.
Since CANFAIL is new, IOCs are not available. Detection must focus on behavior.
command_line_patternpowershell.exe -encnetwork_traffic_patternprocess_namerundll32.exerundll32.exe for suspicious parent processes or for making network connections, as it is often abused to run malicious DLLs.event_idwinword.exe spawning powershell.exe).Detection:
Immediate Actions:
Strategic Improvements:
Use EDR solutions that can detect and block malicious behaviors associated with novel malware, rather than relying on signatures.
Segment critical networks (like OT) from IT networks to prevent lateral movement and contain breaches.
Continuously train users to spot and report sophisticated spearphishing emails.
Since CANFAIL is novel malware, signature-based detection is ineffective. The primary defense is behavioral analysis at the endpoint. A robust Endpoint Detection and Response (EDR) solution must be deployed to monitor process execution chains. For this specific threat, the EDR should be tuned to alert on TTPs common in Ukrainian campaigns, such as a Microsoft Word document (winword.exe) spawning a PowerShell process (powershell.exe), which then makes an outbound network connection. By analyzing the behavior—the 'what it does' rather than the 'what it is'—security teams can detect CANFAIL and similar unknown threats based on their malicious actions, regardless of their file hash.
Even if the malware gets onto an endpoint, it still needs to communicate with its command-and-control (C2) server. By implementing Network Traffic Analysis, security teams can detect the C2 beaconing. This involves monitoring for unusual patterns, even in encrypted traffic. For a threat like CANFAIL, analysts should hunt for connections from sensitive networks (defense, energy) to newly registered domains or IP addresses with no history or poor reputation. Analyzing metadata like connection frequency (e.g., a beacon every 5 minutes), data volume, and non-standard use of ports (like HTTPS on a non-443 port) can reveal the C2 channel and allow defenders to block the C2 domain/IP, effectively cutting off the malware from its controller.
For the high-value sectors targeted (defense and energy), strong network segmentation is a critical architectural defense. The IT network (used for emails, web browsing) must be strictly isolated from the Operational Technology (OT) network (which controls physical processes). This means there should be no direct path for an attacker to move from a compromised workstation in the IT environment to the control systems in the OT environment. All connections between these zones must pass through a demilitarized zone (DMZ) with multiple layers of inspection and strict access control lists. This ensures that even if a user on the IT network is compromised by CANFAIL via a phishing email, the attacker cannot pivot to disrupt critical energy or defense operations.
Google publishes a report linking a Russian state actor to CANFAIL malware attacks in Ukraine.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.