New 'JanaWare' ransomware targeting Turkish citizens as cybercriminal ecosystem fragments

ANALYST: BIVASH KUMAR NAYAK (CHIEF SECURITY ARCHITECT) • PUBLISHED: Wednesday, 15 April 2026
TLP:GREEN // CDB-GOC STRATEGIC INTELLIGENCE ADVISORY // SENTINEL APEX v30.0
Report ID: CDB-APEX-2026-0415-CD75  |  Classification: TLP:GREEN  |  Published: 2026-04-15 09:18:10 UTC
Prepared By: CyberDudeBivash Global Operations Center (GOC)  |  Distribution: Enterprise / SOC / Executive
MEDIUM TLP:GREEN RISK 4.3/10 ANALYST ASSESSED UNATTRIBUTED [RANSOM] Ransomware / Extortion Operation

CYBERDUDEBIVASH SENTINEL APEX™ // PREMIUM THREAT INTELLIGENCE ADVISORY

New 'JanaWare' ransomware targeting Turkish citizens as cybercriminal ecosystem fragments

Advanced Threat Intelligence Advisory by CyberDudeBivash Sentinel APEX™ — AI-Powered Global Threat Intelligence Infrastructure

CYBERDUDEBIVASH(R) SENTINEL APEX - EXECUTIVE INTELLIGENCE BRIEF
New 'JanaWare' ransomware targeting Turkish citizens as cybercriminal ecosystem fragments
CDB-APEX-2026-0415-CD75
2026-04-15
TLP:GREEN
4.3
Risk Index
0
IOC Count
5
MITRE TTPs
44%
Confidence
MEDIUM
Severity
$32.0M
Est. Financial Impact
TARGETED SECTORS: Healthcare * Manufacturing * Government * Education
ACTOR CLUSTER: UNC-UNKNOWN

1. EXECUTIVE SUMMARY (CISO / BOARD READY)

Overview

The CyberDudeBivash Global Operations Center (GOC) has identified and analyzed a significant cybersecurity event classified as a Ransomware / Extortion Operation with a dynamic risk score of 4.3/10 (MEDIUM). This advisory covers the threat designated as "New 'JanaWare' ransomware targeting Turkish citizens as cybercriminal ecosystem fragments", attributed to tracking cluster UNC-UNKNOWN.

New 'JanaWare' ransomware targeting Turkish citizens as cybercriminal ecosystem fragments Cybercriminals are using a new ransomware strain called JanaWare to target people in Turkey, according to a new report from cybersecurity firm Acronis. The researchers said the ransomware operation has been ongoing since 2020 and is associated with a strain of malware that enforces execution constraints based on system locale and external IP geolocation -- restricting its activity to systems only in Turkey.

The Sentinel APEX AI Engine has processed all available intelligence, extracting no actionable technical indicators extracted from the available intelligence. IOC confidence is assessed at 43.6% based on indicator diversity, source reliability, and actor attribution strength. Security teams in the Healthcare, Manufacturing, Government sectors should treat this advisory as an actionable intelligence requirement.

Business Risk Implications: Organizations exposed to this threat face potential impacts across multiple dimensions including operational disruption, financial losses from incident response and remediation costs, reputational damage from public disclosure, and regulatory penalties under applicable data protection frameworks. Security leaders should evaluate this advisory against their organization's risk appetite and threat exposure profile, engaging executive stakeholders as appropriate based on the assessed severity level. The recommended response actions are detailed in Sections 9, 10, and 11 of this report.

Key Risk Rating

CategoryAssessment
Overall Risk Score 4.3 / 10
Confidence Level Medium (43.6%)
Exploitability Theoretical / Under Analysis
Industry Impact MEDIUM

Strategic Impact Assessment

This threat warrants proactive defensive measures and monitoring. While not immediately critical, failure to address identified risks could lead to escalated exposure over time. Organizations in the Healthcare, Manufacturing, Government sectors face heightened exposure due to the nature of this threat. Regulatory implications under frameworks including GDPR, HIPAA, PCI-DSS, and sector-specific mandates should be evaluated by compliance teams.

2. THREAT LANDSCAPE CONTEXT

Campaign Background

This campaign operates within the broader context of ransomware / extortion operation activity that has been observed across the global threat landscape. Intelligence analysis indicates that threat actors continue to evolve their tactics, techniques, and procedures (TTPs) to exploit emerging vulnerabilities, misconfigured infrastructure, and human factors.

Cybercriminals are using a new ransomware strain called JanaWare to target people in Turkey, according to a new report from cybersecurity firm Acronis. The researchers said the ransomware operation has been ongoing since 2020 and is associated with a strain of malware that enforces execution constraints based on system locale and external IP geolocation -- restricting its activity to systems only in Turkey. The ransom demands are very low, hovering around $200 to $400, and Acronis said the hackers are likely opting for a low-value, high-volume approach. "Despite evidence suggesting the campaign has been active for several years, its regional focus and relatively small-scale operations likely helped it remain largely unnoticed," the researchers said. "This case demonstrates how targeted, localized ransomware campaigns can quietly persist in the threat landscape."

The CyberDudeBivash GOC tracks this activity under its institutional tracking framework, correlating indicators across multiple intelligence sources to establish campaign scope. All attribution and technical claims in this section are derived from the source article and verified intelligence feeds - speculative or unverified claims are clearly labeled as Analyst Assessment rather than confirmed intelligence.

Analyst Assessment: Based on the nature of this advisory and the threat category classification, organizations operating in the Healthcare, Manufacturing, Government sectors should evaluate their exposure to this threat type and validate that relevant controls are active. Consult Section 9 (24-Hour IR Plan) for immediate response guidance.

Threat Actor Profile

AttributeIntelligence
Tracking ID UNC-UNKNOWN
Aliases Unattributed Threat Actor
Origin Not Yet Attributed
Motivation Under Analysis
Tooling Varies - see technical analysis
Confidence Insufficient data for attribution

Attribution Reconciliation: The CyberDudeBivash GOC employs an Attribution has not been established with sufficient confidence for definitive actor assignment. The CyberDudeBivash GOC tracks this activity as an unattributed cluster pending further technical analysis. Intelligence consumers should treat third-party attribution claims with appropriate skepticism.

ATTACK CHAIN RECONSTRUCTION
Adversary Kill Chain * Stage-by-Stage Analysis
Initial Access T1566/T1110
Phishing email / RDP bruteforce / VPN exploit
Execution T1059
Script execution via PowerShell / WMI / LOLBins
Persistence T1053
Scheduled tasks / Registry run keys / Boot sectors
Defense Evasion T1562
AV disable / Log clearing / Process injection
Credential Access T1003
LSASS dumping / Mimikatz / SAM database
Lateral Movement T1021
Pass-the-hash / SMB / RDP propagation
Data Exfiltration T1048
Archive & exfiltrate before encryption
Impact T1486
Files encrypted * Ransom note deployed * Backups destroyed
GEOLOCATION INTELLIGENCE
Targeted Regions * Threat Activity Distribution
North America
PRIMARY
Global
HIGH
TARGETING SCOPE
GLOBAL CAMPAIGN
N.AMERICA EU M.EAST ASIA CDB SENTINEL APEX - GEOLOCATION INTELLIGENCE MODULE v19.0

3. TECHNICAL ANALYSIS (DEEP-DIVE)

3.1 Infection Chain Reconstruction

Analysis of available intelligence indicates a structured attack methodology consistent with contemporary threat actor operations. The campaign leverages a combination of technical exploitation and operational security measures designed to maintain prolonged access while minimizing detection probability.

The attack chain progresses through initial access, execution, persistence establishment, and objective completion phases. Each phase employs techniques mapped to the MITRE ATT&CK framework (detailed in Section 5), enabling defenders to identify detection opportunities at multiple points in the kill chain.

[Initial Access] -> [Reconnaissance] -> [Lateral Movement] -> [Privilege Escalation] -> [Data Exfiltration] -> [Encryption Deployment] -> [Ransom Demand]

3.2 Malware / Payload Analysis

Analysis of associated indicators reveals technical characteristics consistent with ransomware / extortion operation operations.

The ransomware payload employs hybrid encryption combining asymmetric RSA key exchange with symmetric AES-256 for file encryption, ensuring decryption is computationally infeasible without the attacker's private key. Pre-encryption activity includes shadow copy deletion via vssadmin and wmic, backup service termination, and security tool disabling. The binary demonstrates anti-analysis techniques including mutex creation, environment fingerprinting, and domain-joined checks. Data exfiltration occurs prior to encryption to enable double-extortion pressure. Ransom notes deploy to affected directories with Tor-based payment and negotiation portals.

3.3 Infrastructure Mapping

No specific network infrastructure indicators were extracted from the available intelligence for this advisory. This commonly occurs with: (1) threat actors using legitimate cloud services (Google Drive, OneDrive, Discord, Telegram) for C2 communication; (2) rapidly rotating infrastructure that has been taken offline since initial reporting; or (3) advisory categories such as vulnerability disclosures where C2 infrastructure is not part of the threat scope. Defenders should prioritize behavioral detection methods from Section 6 rather than IOC-based blocking when network indicators are unavailable.

4. INDICATORS OF COMPROMISE (IOC SECTION)

Structured IOC Table

TypeIndicator ConfidenceFirst Seen
No actionable IOCs were extracted from the available intelligence for this campaign. This may indicate obfuscated infrastructure, use of legitimate services, or intelligence that requires deeper analysis. Monitor for updates as additional intelligence becomes available.
Behavioral Detection Guidance (When IOCs Are Unavailable):
When traditional IOCs are limited, defenders should prioritize behavioral detection strategies: (1) Deploy the Sigma and YARA rules from Section 6 which target adversary TTPs rather than static indicators; (2) Focus hunting efforts on the MITRE ATT&CK techniques in Section 5 using the KQL/SPL queries provided; (3) Monitor for anomalous authentication patterns, suspicious token activity, and unusual API calls; (4) Correlate endpoint behavioral telemetry with identity provider logs for adversary-in-the-middle detection. As additional intelligence becomes available, this section will be updated with extracted indicators.

Detection Recommendations

  • Network Layer: Block identified IP addresses and domains at firewall and DNS proxy level. Implement DNS sinkholing for known malicious domains to prevent C2 callbacks.
  • Endpoint Layer: Configure EDR rules to detect shadow copy deletion (vssadmin, wmic), mass file encryption patterns, service termination commands, and backup destruction. Monitor for lateral movement tools (PsExec, WMI, RDP brute-force) across the network.
  • Email Security: Update email gateway rules to detect associated phishing patterns. Implement DMARC/SPF/DKIM enforcement for impersonated domains.
  • SIEM Correlation: Integrate the provided Sigma rules into SIEM platforms for real-time alerting. Correlate network IOCs with endpoint telemetry for campaign detection.

5. MITRE ATT&CK(R) MAPPING

The following MITRE ATT&CK(R) techniques have been identified through automated analysis of the threat intelligence associated with this campaign. Each technique represents a documented adversary behavior that defenders can use to build detection and response capabilities.

TacticTechnique IDContext
Initial Access Phishing T1566 Phishing emails with malicious attachments or links
Execution Malicious File T1204.002 Adversary behavior detected through intelligence correlation
Defense Evasion Obfuscated Files or Information T1027 Encoding or encryption to evade detection
Exfiltration Exfiltration Over Web Service T1567 Exfiltration through cloud/web services
Impact Data Encrypted for Impact T1486 Data encryption for ransomware impact

6. DETECTION ENGINEERING (SOC READY)

6.1 Sigma Rules

The following Sigma rule provides SIEM-agnostic detection capability for this campaign. Deploy to Microsoft Sentinel, Splunk, Elastic, or any Sigma-compatible platform.

title: 'CDB-Sentinel: New JanaWare ransomware targeting Turkish citizens as cybercriminal ecosystem fr - Ransomware Behavioral Detection' id: cdb-983027 status: experimental description: 'Detects ransomware TTPs associated with: New JanaWare ransomware targeting Turkish citizens as cybercriminal ecosystem fr.' author: CyberDudeBivash GOC (Automated) date: 2026/04/15 tags: - attack.impact.t1486 - attack.defense_evasion logsource: category: process_creation product: windows detection: selection: Image|endswith: - vssadmin.exe - wbadmin.exe - bcdedit.exe - wmic.exe - cmd.exe CommandLine|contains: - delete shadows - delete catalog - recoveryenabled no - shadowcopy delete condition: selection falsepositives: - Legitimate backup management level: critical

6.2 YARA Rules

Deploy this YARA rule for memory and disk forensics scanning across endpoints. Compatible with YARA-enabled EDR solutions and standalone YARA scanning.

rule CDB_New__JanaWare__ransomware_targeting_Turk { meta: author = "CyberDudeBivash GOC" description = "Detects indicators associated with: New 'JanaWare' ransomware targeting Turkish citizens as cybe" date = "2026-04-15" reference = "https://cyberbivash.blogspot.com" severity = "high" tlp = "TLP:CLEAR" strings: $beh0 = "vssadmin delete shadows" ascii wide nocase $beh1 = "bcdedit /set" ascii wide nocase $beh2 = ".onion" ascii wide $beh3 = "YOUR FILES HAVE BEEN" ascii wide nocase condition: uint16(0) == 0x5A4D and filesize < 10MB and 2 of them }

6.3 SIEM Queries

Microsoft Sentinel (KQL):

// CDB-Sentinel: Behavioral hunt for New 'JanaWare' ransomware targeting Turkish citize DeviceProcessEvents | where Timestamp > ago(7d) | where ProcessCommandLine has_any ("powershell", "cmd.exe", "curl", "wget") | where FolderPath has_any ("AppData", "Temp", "ProgramData") | project Timestamp, DeviceName, ProcessCommandLine, InitiatingProcessFileName | sort by Timestamp desc

Splunk SPL:

| index=* sourcetype=syslog OR sourcetype=wineventlog | search process_name IN ("powershell.exe","cmd.exe","wscript.exe") | where match(cmdline,"(?i)(download|invoke|base64|hidden)") | table _time host process_name cmdline | sort -_time

6.4 Network Detection

Monitor network traffic for connections to identified infrastructure. Implement the following Suricata/Snort compatible rule for network-level detection:

# CDB-Sentinel: Behavioral detection for New 'JanaWare' ransomware targeting Turk alert http any any -> any any (msg:"CDB-Sentinel Suspicious User-Agent"; \ content:"Mozilla/5.0"; http.user_agent; \ content:"PowerShell"; http.user_agent; \ sid:9999; rev:1;)

7. VULNERABILITY & EXPLOIT ANALYSIS

No specific CVE identifiers were associated with this advisory at the time of publication. However, organizations should maintain awareness that threat actors frequently exploit recently disclosed vulnerabilities as part of ransomware / extortion operation operations. Continuous vulnerability scanning and risk-based patch prioritization remain critical defensive requirements regardless of whether specific CVEs are referenced in individual advisories.

8. RISK SCORING METHODOLOGY

The CyberDudeBivash Sentinel APEX Risk Engine calculates threat risk scores using a weighted multi-factor analysis model. This transparent methodology ensures that all risk assessments are reproducible, defensible, and aligned with enterprise risk management frameworks. The scoring formula considers the following dimensions:

FactorWeightThis Advisory
IOC Diversity (categories found)0.5 per category 0 categories
File Hash Indicators (SHA256/MD5)+1.5 Not detected
Network Indicators (IP/Domain)+1.0/+0.8 0 IPs, 0 Domains
MITRE ATT&CK Techniques0.3 per technique 5 techniques mapped
Actor Attribution+1.0 if known UNC-UNKNOWN
CVSS/EPSS Integration+2.0/+1.5 N/A
FINAL SCORE 4.3/10

This scoring methodology provides full transparency into how risk assessments are calculated, enabling security teams to validate findings and adjust organizational response priorities based on their specific risk appetite and threat exposure profile.

9. 24-HOUR INCIDENT RESPONSE PLAN

Organizations that identify exposure to this threat should execute the following immediate containment actions within the first 24 hours of detection:

  • Network Segmentation: Isolate affected network segments to prevent lateral movement. Implement emergency firewall rules blocking all identified IOCs at perimeter and internal boundaries.
  • IOC Blocking: Deploy all indicators from Section 4 to firewalls, web proxies, DNS filters, and endpoint protection platforms immediately. Prioritize IP and domain blocking.
  • Credential Resets: Force password resets for any accounts that may have been exposed. Revoke active sessions and API tokens for compromised or potentially compromised accounts.
  • Endpoint Scanning: Execute full disk and memory scans using updated YARA rules (Section 6.2) across all endpoints in the affected environment. Prioritize servers and privileged workstations.
  • Forensic Capture: Preserve evidence by capturing memory dumps, disk images, and network packet captures from affected systems before any remediation actions that could alter evidence.
  • Threat Hunting: Conduct proactive hunting using the SIEM queries from Section 6.3 to identify any historical compromise that predates detection.

10. 7-DAY REMEDIATION STRATEGY

Following initial containment, execute this structured remediation plan over the subsequent 7 days to ensure comprehensive threat elimination and hardening:

  • Day 1-2 - MFA Enforcement: Deploy FIDO2-compliant multi-factor authentication across all external-facing and privileged accounts. Disable legacy authentication protocols (NTLM, Basic Auth).
  • Day 2-3 - Patch Deployment: Accelerate patching for all vulnerabilities referenced in this advisory. Prioritize internet-facing systems and those with known exploit availability.
  • Day 3-5 - Access Policy Hardening: Review and tighten conditional access policies. Implement Just-In-Time (JIT) access for administrative functions. Audit service accounts.
  • Day 5-6 - Threat Hunting Sweep: Conduct comprehensive threat hunting across the enterprise using behavioral indicators from the MITRE ATT&CK mappings in Section 5.
  • Day 6-7 - Log Retention Review: Ensure logging coverage meets forensic investigation requirements (minimum 90-day retention). Verify SIEM ingestion of all critical data sources.

11. STRATEGIC RECOMMENDATIONS

Beyond immediate incident response, organizations should evaluate the following strategic security improvements to reduce exposure to similar future threats:

  • Zero Trust Architecture: Transition from perimeter-based security to a Zero Trust model that verifies every access request regardless of source location. Implement micro-segmentation.
  • Behavioral Detection: Supplement signature-based detection with behavioral analytics capable of identifying novel attack techniques and living-off-the-land attacks.
  • Threat Intelligence Integration: Subscribe to curated threat intelligence feeds and integrate automated IOC ingestion into SIEM/SOAR platforms for real-time protection.
  • Security Awareness: Conduct targeted phishing simulation exercises for employees. Implement continuous security awareness training with measurable effectiveness metrics.
  • SOC Automation: Deploy SOAR playbooks for automated triage and response to common threat scenarios. Reduce mean time to detect (MTTD) and respond (MTTR).
  • Supply Chain Security: Implement vendor risk assessment frameworks and continuous monitoring of third-party software dependencies for emerging vulnerabilities.

12. INDUSTRY-SPECIFIC GUIDANCE

Different industries face unique risk profiles from this threat. The following targeted guidance addresses sector-specific considerations:

Financial Services

Ensure PCI-DSS compliance requirements are met for all systems in scope. Implement transaction monitoring for anomalous patterns. Review and strengthen API security for digital banking platforms. Coordinate with FS-ISAC for sector-specific intelligence sharing.

Healthcare

Verify HIPAA-compliant security controls around electronic health records (EHR) systems. Isolate medical device networks from general IT infrastructure. Ensure backup systems are operational and tested for ransomware scenarios.

Government

Align response with CISA directives and BOD requirements. Review FedRAMP authorized service configurations. Coordinate with sector-specific ISACs. Implement enhanced monitoring on .gov and .mil domains.

Technology / SaaS

Review CI/CD pipeline security. Audit third-party dependencies for vulnerability exposure. Implement enhanced monitoring on customer-facing APIs. Review incident communication plans for customer notification.

Manufacturing / Critical Infrastructure

Isolate OT/ICS networks from IT infrastructure. Review remote access policies for industrial control systems. Implement enhanced monitoring at IT/OT boundaries.

Education

Review student and faculty data protection controls. Monitor for credential-based attacks against identity providers. Ensure research data repositories are adequately segmented.

13. GLOBAL THREAT TRENDS CONNECTION

Ransomware-as-a-service (RaaS) operations continue to dominate the threat landscape, with affiliate programs enabling less-skilled actors to deploy sophisticated ransomware payloads. Double and triple extortion tactics - encrypting data, threatening public disclosure, and targeting backup infrastructure simultaneously - have become standard operating procedure. The healthcare, manufacturing, and critical infrastructure sectors remain primary targets due to operational disruption tolerance and willingness to pay ransoms.

This advisory connects to the broader pattern of Ransomware / Extortion Operation activity tracked by the CyberDudeBivash GOC. Organizations that invest in behavioral detection capabilities, continuous threat intelligence integration, and security automation are best positioned to defend against the evolving threat landscape. Proactive, intelligence-driven security operations represent the most impactful strategic investment available to security leaders in the current environment.

Intelligence Confidence Note: Trend assessments in this section are based on CyberDudeBivash GOC analysis of published threat reports, CISA advisories, and multi-source intelligence feeds. Individual threat actor TTPs may vary from general trends described.

14. CYBERDUDEBIVASH AUTHORITY SECTION

This intelligence advisory is produced by the CyberDudeBivash Global Operations Center (GOC), a dedicated research division focused on AI-driven threat intelligence, enterprise detection engineering, and advanced cyber defense automation. Our platform processes intelligence from multiple high-authority sources to deliver actionable, timely, and comprehensive threat assessments for security professionals worldwide.

Enterprise Services:

  • Custom Threat Monitoring & Intelligence Briefings
  • Managed Detection & Response (MDR) Support
  • Private Intelligence Briefings for Executive Teams
  • Red Team & Blue Team Assessment Services
  • SOC Automation & Detection Engineering Consulting

Contact: bivash@cyberdudebivash.com  |  Phone: +91 8179881447  |  Web: https://www.cyberdudebivash.com

15. INTELLIGENCE KEYWORDS & TAXONOMY

Threat Intelligence Platform * SOC Detection Engineering * MITRE ATT&CK Mapping * IOC Analysis * CVE Deep Dive * AI Cybersecurity * Malware Analysis Report * Enterprise Threat Advisory * Cyber Threat Intelligence * Incident Response * Digital Forensics * STIX 2.1 * Sigma Rules * YARA Rules * CyberDudeBivash * Sentinel APEX * ransomware * targeting * Turkish * citizens

16. APPENDIX

Source Reference: https://therecord.media/new-janaware-ransomware-targeting-turkey

STIX 2.1 Bundle: Available via the CyberDudeBivash Threat Intel Platform JSON feed.

IOC Format: Structured JSON export available for SIEM/SOAR integration.

Report Version: v30.0 | Generated by Sentinel APEX AI Engine

CyberDudeBivash(R) - AI-Powered Global Threat Intelligence

This advisory is produced by the CyberDudeBivash Pvt. Ltd. Global Operations Center. Intelligence correlation, risk scoring, and detection engineering are powered by the Sentinel APEX AI Engine.

Explore CyberDudeBivash Platform ->

(C) 2026 CyberDudeBivash Pvt. Ltd. // CDB-GOC-01 // Bhubaneswar, India