Security intelligence firm CYFIRMA has released a report detailing two newly discovered malware families targeting Microsoft Windows systems. The first, named KansasGroup ransomware, is a variant that encrypts victim files, appends the .kansas4life extension, and drops a ransom note named KANSASGROUP.txt. The second, CNBackdoor, is a more sophisticated and stealthy backdoor designed for long-term persistence. CNBackdoor operates in multiple stages, using hidden PowerShell processes to disable security products like Microsoft Defender before establishing a resilient foothold on the compromised system. The emergence of these threats highlights the continued evolution of both financially motivated ransomware and espionage-focused backdoors.
.kansas4life to encrypted files.KANSASGROUP.txt in affected directories. The note instructs the victim to contact the attackers via a peer-to-peer communication platform and provides a unique ID. It does not specify a ransom amount.While both malware families target Windows, they represent two different attacker objectives: immediate financial gain versus long-term strategic access.
T1486 - Data Encrypted for Impact: The core functionality of the malware.T1083 - File and Directory Discovery: The malware must scan the file system to find files to encrypt.T1490 - Inhibit System Recovery: While not explicitly stated, most modern ransomware attempts to delete shadow copies or backups.T1059.001 - PowerShell: Used extensively for defense evasion and execution.T1562.001 - Disable or Modify Tools: The key behavior of adding exclusions to Microsoft Defender.T1112 - Modify Registry: Often used in conjunction with PowerShell to set exclusions.T1547.001 - Registry Run Keys / Startup Folder: A likely method for establishing persistence.T1071.001 - Web Protocols: The backdoor will need to use standard web protocols (HTTP/S) for its C2 communication to remain stealthy.The stealth of CNBackdoor is its primary feature. By disabling security tools first, it aims to operate undetected for long periods, maximizing the attacker's opportunity to achieve their objectives.
.kansas4lifeKANSASGROUP.txttommysbakescodes.wspowershell.exe -Command Add-MpPreference -ExclusionPathKANSASGROUP.txtHKLM\SOFTWARE\Microsoft\Windows Defender\Exclusionstommysbakescodes.wsProcess Analysis (D3-PA).Application Hardening (D3-AH).The most effective defense against the KansasGroup ransomware is to maintain tested, offline backups.
Use EDR/antivirus with tamper protection enabled to prevent malware like CNBackdoor from disabling it.
Enable and audit PowerShell logs to detect malicious script execution and defense evasion techniques.
Use application control policies to restrict the execution of unauthorized scripts and executables.
To detect and counter the stealthy CNBackdoor, organizations must employ advanced Process Analysis (D3-PA), particularly focused on PowerShell. Security teams should configure their EDR and SIEM to alert on any process, especially non-administrative ones, that spawns PowerShell with command-line arguments to modify security settings. A high-fidelity alert should be created for any execution of Add-MpPreference -ExclusionPath. Furthermore, by enabling PowerShell Script Block Logging (Event ID 4104), the full content of the malicious script is logged, allowing for detailed analysis and signature creation. Monitoring the parent-child process relationships is also key; a legitimate installer should not be spawning a hidden PowerShell window to modify Defender settings. This focus on behavioral anomalies is crucial for catching stealthy malware that avoids traditional signature-based detection.
The definitive countermeasure for the KansasGroup ransomware is a resilient Data Backup (D3-DB) strategy. Organizations must ensure they have regular, automated backups of all critical data. These backups must follow the 3-2-1 rule: three copies, on two different media, with at least one copy offline or immutable. 'Immutable' storage (e.g., in AWS S3 with Object Lock) prevents the ransomware from encrypting or deleting the backups, even if it compromises an administrator account. Regular, automated testing of these backups by attempting to restore a sample set of data is non-negotiable. A successful backup strategy completely neutralizes the encryption threat of the ransomware, allowing the organization to restore its data and operations without considering payment, turning a potential disaster into a manageable recovery process.
To proactively defend against backdoors like CNBackdoor that abuse legitimate tools, organizations should implement Application Hardening (D3-AH) for PowerShell. This involves using Group Policy to enable PowerShell Constrained Language Mode for all standard users. In this mode, users can only run a limited, core set of PowerShell cmdlets, and cannot execute arbitrary scripts or access .NET functions, which would block many of the backdoor's capabilities. Additionally, EDR solutions should have tamper protection enabled and enforced. This feature prevents any user or process, including malware, from stopping the security agent's service or modifying its configuration on the endpoint, thus countering the malware's attempt to disable security controls.

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.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
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.