Back to Intelligence

MAJINAHANASHI Ransomware Gang: 2 New Victims Posted — Campaign Analysis & Detection Engineering

SA
Security Arsenal Team
August 30, 2026
10 min read

Classification: TLP:CLEAR | Report Date: 2026-08-30 | Source: ransomware.live monitoring of MAJINAHANASHI .onion leak site


Executive Summary

Security Arsenal's dark web monitoring confirms 2 new victim postings attributed to the MAJINAHANASHI ransomware operation on 2026-08-29. While victim sector and country metadata remains obfuscated on the leak site (listed as "Not Found" / "?"), the postings span multiple countries, consistent with an opportunistic, broad-targeting campaign rather than a sector-focused operation. The low posting volume (2 in the last 100 indexed postings) suggests either an emerging/rebranding group, a group in an operational pause, or deliberate victim-list throttling during active negotiations.

Organizations with exposed Check Point gateways, ConnectWise ScreenConnect instances, unpatched Exchange servers, or developer tooling (Nx Console) should treat this bulletin as an immediate action item.


1. Threat Actor Profile — MAJINAHANASHI

AttributeAssessment
AliasesNo confirmed aliases; name pattern suggests Japanese transliteration ("magician/illusionist"), a known tactic among rebranded crews seeking to shed prior sanctions exposure
Operating ModelAssessed as RaaS or semi-closed affiliate model; low posting cadence is typical of groups running 2–5 active affiliates rather than industrial-scale operations
Ransom DemandsUnconfirmed for this group; comparable low-volume crews typically demand $150K–$2M USD scaled to victim revenue, payable in BTC/XMR
Initial AccessConsistent with current ecosystem TTPs: exploitation of edge VPN appliances (Check Point IKEv1 auth bypass), exposed RDP, and trojanized developer tooling (supply chain)
Extortion ModelDouble extortion — leak site presence confirms data-theft-before-encryption playbook; victims posted on 2026-08-29 indicate failed negotiation or non-payment within ~7–21 days of intrusion
Dwell TimeIndustry baseline for comparable groups: 5–14 days from initial access to encryption, with exfiltration occurring in the final 72 hours

Analyst Note: The victim naming pattern (partial redaction: TERRA*** & MON****) indicates MAJINAHANASHI uses staggered disclosure — a pressure tactic where full names are released if payment deadlines lapse. One victim, MONTCAU, is already fully disclosed, suggesting that negotiation thread collapsed.


2. Current Campaign Analysis

Victimology

  • Sectors: Not disclosed in leak site metadata. The partial name "TERRA" suggests possible real estate, agriculture, or geospatial/energy verticals; "MONTCAU" is consistent with a European (possibly Catalan/Spanish) municipality, hospitality group, or construction firm. Municipal and mid-market construction/hospitality entities are high-probability profiles based on naming conventions.
  • Geography: Multi-country, no concentration disclosed — opportunistic targeting consistent with edge-device exploitation rather than spear-phishing against a specific vertical.
  • Victim Size: Based on comparable low-volume crew patterns, expect SMB-to-mid-market (50–2,500 employees, $10M–$500M revenue) — organizations large enough to pay but typically lacking 24/7 SOC coverage.

Posting Cadence & Escalation

  • 2 postings in a single day (2026-08-29) after a quiet index period indicates a synchronized leak event — multiple intrusions likely detonated within the same operational window (typical of a single affiliate batch).
  • Watch for escalation: groups at this maturity stage often follow a 2-posting day with 3–5 additional victims within 7 days as parallel negotiations expire.

CVE Correlation — Probable Initial Access Vectors

The following CISA KEV entries with confirmed ransomware use align with MAJINAHANASHI's assessed access methods:

CVEProductRelevance
CVE-2026-50751Check Point Security Gateway (IKEv1 improper auth)Primary suspect — edge VPN bypass enables unauthenticated access; matches multi-country opportunistic pattern
CVE-2026-48027Nx Console (embedded malicious code)Supply-chain vector — developer workstations as beachhead, common for reaching build servers and cloud credentials
CVE-2024-1708ConnectWise ScreenConnect (path traversal → RCE)RMM tooling abuse — direct ransomware operator access channel
CVE-2025-60710Windows link following (privesc)Post-compromise privilege escalation to SYSTEM/Domain Admin
CVE-2023-21529Exchange deserialization (RCE)On-prem Exchange as initial foothold and mailbox-based exfil staging

Assessment: CVE-2026-50751 (Check Point) is the highest-confidence initial access vector given the multi-country, multi-victim single-day posting pattern characteristic of mass edge-device scanning.


3. Detection Engineering

Sigma Rules

YAML
---
title: Check Point VPN Improper Authentication Exploitation Attempt (CVE-2026-50751)
id: 8f3a2c1e-7b4d-4e9a-b2f1-9c6d5e4a3b21
status: experimental
description: Detects anomalous IKEv1 key exchange authentication events consistent with CVE-2026-50751 exploitation used as initial access by ransomware operators including MAJINAHANASHI
author: Security Arsenal Threat Intelligence
date: 2026/08/30
references:
    - https://www.cisa.gov/known-exploited-vulnerabilities-catalog
logsource:
    product: checkpoint
    service: vpn
detection:
    selection_auth_fail:
        action: 'key_exchange'
        ike_version: 'IKEv1'
        auth_result: 'failed'
    selection_anomaly:
        src_ip|cidr:
            - '0.0.0.0/0'
    filter_internal:
        src_ip|cidr:
            - '10.0.0.0/8'
            - '172.16.0.0/8'
            - '192.168.0.0/16'
    condition: selection_auth_fail and selection_anomaly and not filter_internal
falsepositives:
    - Misconfigured remote clients
    - Legacy IKEv1 site-to-site tunnel negotiation
level: high
tags:
    - attack.initial_access
    - attack.t1190
    - attack.t1133
    - cve.2026.50751
---
title: Ransomware Pre-Encryption Staging - Volume Shadow Copy Deletion
id: 2b7d9e4f-1a3c-4d8b-9e2f-5c8a6b3d7e19
status: stable
description: Detects deletion or resizing of Volume Shadow Copies via vssadmin, wmic, or PowerShell - a near-universal pre-encryption step in ransomware playbooks including MAJINAHANASHI double-extortion operations
author: Security Arsenal Threat Intelligence
date: 2026/08/30
logsource:
    category: process_creation
    product: windows
detection:
    selection_vssadmin:
        Image|endswith: '\vssadmin.exe'
        CommandLine|contains:
            - 'delete shadows'
            - 'resize shadowstorage'
    selection_wmic:
        Image|endswith: '\wmic.exe'
        CommandLine|contains: 'shadowcopy delete'
    selection_powershell:
        Image|endswith:
            - '\powershell.exe'
            - '\pwsh.exe'
        CommandLine|contains:
            - 'Remove-WmiObject'
            - 'Get-WmiObject Win32_Shadowcopy'
            - 'Delete()'
    condition: 1 of selection_*
falsepositives:
    - Legitimate backup maintenance scripts
    - IT storage reclamation tasks
level: critical
tags:
    - attack.impact
    - attack.t1490
    - attack.defense_evasion
---
title: PsExec or WMI Remote Execution - Ransomware Lateral Movement
id: 5c1e8a3d-9f2b-4a7c-8d1e-3b6f9a2c5d84
status: stable
description: Detects remote service creation via PsExec-named pipes or WMI process creation commonly used by ransomware affiliates for mass encryption deployment across domain assets
author: Security Arsenal Threat Intelligence
date: 2026/08/30
logsource:
    product: windows
    service: system
    definition: 'Event ID 7045 service installation'
detection:
    selection_event:
        EventID: 7045
    selection_psexec:
        ServiceName|contains:
            - 'PSEXESVC'
            - 'PAExec'
            - 'csexec'
    selection_suspicious_path:
        ImagePath|contains:
            - '\ADMIN$\'
            - '\Temp\'
            - '\Users\Public\'
        ImagePath|endswith: '.exe'
    condition: selection_event and (selection_psexec or selection_suspicious_path)
falsepositives:
    - Legitimate administrative remote management
    - Software deployment tools (SCCM, PDQ)
level: high
tags:
    - attack.lateral_movement
    - attack.t1021.002
    - attack.t1569.002

KQL — Microsoft Sentinel Hunt: Pre-Ransomware Staging & Exfiltration

KQL — Microsoft Sentinel / Defender
// MAJINAHANASHI-style pre-encryption staging hunt
// Looks for: shadow copy tampering + mass file staging + suspicious outbound volume within 72h window
let lookback = 7d;
let staging_window = 72h;
// Signal 1: Shadow copy deletion / backup tampering
let ShadowTamper = DeviceProcessEvents
| where TimeGenerated > ago(lookback)
| where ProcessCommandLine has_any ("vssadmin delete shadows", "shadowcopy delete", "resize shadowstorage", "bcdedit", "wbadmin delete")
| project ShadowTime=TimeGenerated, DeviceName, AccountName, ProcessCommandLine;
// Signal 2: Archive creation in user-writable dirs (data staging)
let Staging = DeviceFileEvents
| where TimeGenerated > ago(lookback)
| where FolderPath has_any ("\\Users\\Public\\", "\\ProgramData\\", "\\Temp\\")
| where FileName endswith_any (".zip", ".rar", ".7z", ".tar.gz")
| project StageTime=TimeGenerated, DeviceName, FileName, FolderPath, InitiatingProcessAccountName;
// Signal 3: Large outbound transfers to uncommon destinations (exfil)
let Exfil = DeviceNetworkEvents
| where TimeGenerated > ago(lookback)
| where RemoteUrl has_any ("mega.nz", "transfer.sh", "file.io", "anonfiles", "gofile.io", "temp.sh")
    or RemotePort in (21, 22, 443) and ActionType == "ConnectionSuccess" and InitiatingProcessName in~ ("rclone.exe", "megasync.exe", "winscp.exe", "filezilla.exe")
| project ExfilTime=TimeGenerated, DeviceName, InitiatingProcessName, RemoteUrl, RemoteIP, RemotePort;
// Correlate devices showing 2+ signals within the staging window
ShadowTamper
| join kind=inner Staging on DeviceName
| where datetime_diff('hour', StageTime, ShadowTime) between (0 .. 72)
| join kind=leftouter Exfil on DeviceName
| summarize FirstActivity=min(ShadowTime), LastActivity=max(ExfilTime), Signals=count(),
            Accounts=make_set(AccountName), StagedFiles=make_set(FileName), ExfilDestinations=make_set(RemoteUrl)
  by DeviceName
| sort by Signals desc, FirstActivity asc

PowerShell — Rapid Response: RDP Exposure + Recent Persistence Audit

PowerShell
# MAJINAHANASHI Rapid Triage Script - run on domain controllers and edge-facing servers
# Checks: RDP exposure, scheduled tasks (7d), shadow copy integrity, new local admins
# Requires: Run as Administrator

$report = @()
$cutoff = (Get-Date).AddDays(-7)

Write-Host "=== [1] RDP EXPOSURE CHECK ===" -ForegroundColor Cyan
$rdpEnabled = (Get-ItemProperty 'HKLM:\System\CurrentControlSet\Control\Terminal Server').fDenyTSConnections -eq 0
$nlaEnabled = (Get-ItemProperty 'HKLM:\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -ErrorAction SilentlyContinue).UserAuthentication -eq 1
$rdpPort = (Get-NetTCPConnection -LocalPort 3389 -State Listen -ErrorAction SilentlyContinue | Measure-Object).Count
$report += [pscustomobject]@{Check="RDP_Enabled"; Risk=$(if($rdpEnabled){"HIGH"}else{"OK"}); Detail="fDenyTSConnections=$($rdpEnabled -eq $false)"}
$report += [pscustomobject]@{Check="NLA_Enforced"; Risk=$(if($rdpEnabled -and -not $nlaEnabled){"HIGH"}else{"OK"}); Detail="NLA=$nlaEnabled"}
$report += [pscustomobject]@{Check="RDP_Listening"; Risk=$(if($rdpPort -gt 0){"REVIEW"}else{"OK"}); Detail="Listeners=$rdpPort"}

Write-Host "=== [2] SCHEDULED TASKS (LAST 7 DAYS) ===" -ForegroundColor Cyan
Get-ScheduledTask | Where-Object { $_.Date -and ([datetime]$_.Date) -gt $cutoff } | ForEach-Object {
    $report += [pscustomobject]@{Check="NewScheduledTask"; Risk="REVIEW"; Detail="$($_.TaskName) | $($_.TaskPath) | Created=$($_.Date)"}
}

Write-Host "=== [3] VOLUME SHADOW COPY INTEGRITY ===" -ForegroundColor Cyan
$shadows = Get-CimInstance Win32_ShadowCopy -ErrorAction SilentlyContinue
$report += [pscustomobject]@{Check="ShadowCopies"; Risk=$(if(-not $shadows){"CRITICAL - may indicate T1490 tampering"}else{"OK"}); Detail="Count=$(@($shadows).Count)"}

Write-Host "=== [4] NEW LOCAL ADMINISTRATORS (7d) ===" -ForegroundColor Cyan
Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4732; StartTime=$cutoff} -ErrorAction SilentlyContinue |
  Where-Object { $_.Message -match 'Administrators' } | ForEach-Object {
    $report += [pscustomobject]@{Check="AdminGroupChange"; Risk="HIGH"; Detail="$($_.TimeCreated) | $($_.Message.Substring(0,[Math]::Min(200,$_.Message.Length)))"}
}

Write-Host "=== [5] SUSPICIOUS RMM / EXFIL TOOLING ===" -ForegroundColor Cyan
$tools = @('rclone.exe','megasync.exe','winscp.exe','filezilla.exe','psexec.exe','screenconnect*.exe','anydesk.exe')
foreach ($t in $tools) {
    Get-ChildItem -Path C:\ -Recurse -Filter $t -ErrorAction SilentlyContinue -Depth 4 | ForEach-Object {
        $report += [pscustomobject]@{Check="SuspiciousTool"; Risk="REVIEW"; Detail=$_.FullName}
    }
}

$report | Sort-Object Risk | Format-Table -AutoSize
$report | Export-Csv -Path ".\MAJINAHANASHI_triage_$(Get-Date -Format 'yyyyMMdd_HHmm').csv" -NoTypeInformation
Write-Host "Report exported. Investigate any CRITICAL/HIGH findings before assuming host is clean." -ForegroundColor Yellow

4. Incident Response Priorities

T-Minus Detection Checklist (Before Encryption Fires)

  • Check Point VPN logs: IKEv1 authentication anomalies from single external IPs in the last 30 days (CVE-2026-50751)
  • vssadmin/wmic/bcdedit execution on any server — this is your loudest pre-detonation alarm
  • New services installed via ADMIN$ or PSEXESVC appearing on >5 hosts within 1 hour (mass deployment staging)
  • Archive files (.zip/.7z) appearing in C:\ProgramData or C:\Users\Public on file servers
  • Outbound connections to MEGA, GoFile, transfer.sh, or unknown IPs on 443 with rclone/megasync process lineage
  • Batch logons (Type 3/10) from a single admin account touching dozens of hosts — credential theft in motion

Assets This Gang-Profile Prioritizes for Exfiltration

  1. File servers / NAS — contracts, financials, HR data (leverage for double extortion)
  2. Exchange mailboxes (on-prem) — executive correspondence; CVE-2023-21529 exposure increases risk
  3. Backup infrastructure credentials — targeted to blind recovery capability
  4. Domain controllers — NTDS.dit theft for full credential compromise

Containment Actions (Ordered by Urgency)

  1. Isolate affected VLANs/hosts at the switch level — do NOT wait for full scoping
  2. Disable compromised accounts and force enterprise-wide credential reset for any account seen in lateral movement telemetry
  3. Block exfil egress at the proxy/firewall: rclone, MEGA, GoFile, unknown 443 destinations
  4. Snapshot/preserve volatile evidence on the patient-zero host before AV remediation wipes artifacts
  5. Verify backup integrity offline before declaring recovery readiness — assume backup admin creds are burned
  6. Check Point gateways: take IKEv1 portals offline or apply the vendor fix for CVE-2026-50751 immediately if unpatched

5. Hardening Recommendations

Immediate (24 Hours)

  • Patch Check Point Security Gateway for CVE-2026-50751 or disable IKEv1 remote access until patched — this is the highest-probability door into your network right now
  • Patch/audit ConnectWise ScreenConnect (CVE-2024-1708) and all other internet-facing RMM; enforce MFA on RMM consoles
  • Block macro execution from internet-sourced Office docs via ASR rules; audit Nx Console developer installs for the malicious package version (CVE-2026-48027)
  • Deploy the Sigma rules above to your SIEM; enable the vssadmin deletion alert as CRITICAL paging
  • Verify RDP is not internet-exposed (Shodan your own ASN); enforce NLA + VPN-only RDP

Short-Term (2 Weeks)

  • Segment backup infrastructure onto a dedicated management network with immutable (WORM/object-lock) copies
  • Deploy tiered admin model — eliminate shared local admin passwords; roll out LAPS
  • Egress filtering with TLS inspection on server VLANs; default-deny outbound for domain controllers and file servers
  • Exchange on-prem: patch CVE-2023-21529, restrict EWS/OWA exposure, enable AMSI integration
  • Tabletop a double-extortion scenario with legal, comms, and leadership — decide payment posture and disclosure workflow before you need it

Next Update: Security Arsenal will refresh this bulletin if MAJINAHANASHI posts additional victims within the next 7 days or if sector/geography metadata is disclosed on the leak site.

Related Resources

Security Arsenal Incident Response Managed SOC & MDR Services AlertMonitor Threat Detection From The Dark Side Intel Hub

Is your security operations ready?

Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.