Skip to main content
Darkfield

Ransomware victim disclosure

← All victims

Unknown (SharePoint T1-T4 staged release #1)

Claimed by HELIX · listed 3 hours ago

Today
Age
since listed · listed for ransom

Status timeline

  1. ListedAug 10, 2026

Current state: Listed for ransom

At a glance

Group
HELIX
Status
Listed for ransom
Listed on leak site
Aug 10, 2026

About the victim

AI dossier — public-source company profile

Unknown victim. The leak post references 'Westland' and 'Morguard' as entities that made contact during ransom negotiation but did not proceed with payment or serious engagement.

Attack summary

Severity: medium — Confirmed exfiltration of internal SharePoint data with staged public release mechanism; however, the victim identity is unknown, the data type and sensitivity cannot be assessed, and no proof files or sample data are advertised in this post excerpt.

HELIX claims exfiltration of SharePoint libraries from an unidentified victim, staged across four tiers (T1–T4) with a countdown-based gradual release mechanism. No encryption is mentioned; the threat is data publication only.

medium

Data the group says was taken

AI dossier — extracted from the leak post
  • SharePoint libraries (content unspecified)

What the group claims

SharePoint libraries staged T1 (least) to T4 (most). Release countdown live on Helix. Tiers unlock by stage when each set timer reaches 0.

The leak post

captured from the group's site
Published feeds. Opening a feed leaves this site for the board onion.
[ Westland reached out, got the full demand, then stalled with no serious number. Contacting us and dragging process is not negotiation. ](http://helix2kvkqjzrkh3ospyukij7uemxwvbdmqberjmrudjmqy4hspwzzqd.onion/p/380506d310d5417b836512938f95a302a7fb021fbe54b9f392da079aaf9ade1e) [ Morguard reached out, took extensions, then ignored the negotiation with no real offer. Contacting us and stalling is not a strategy. Deadlines stand. Silence after outreach gets a private board and a countdown then publication. ](http://helix2kvkqjzrkh3ospyukij7uemxwvbdmqberjmrudjmqy4hspwzzqd.onion/p/c986586defd4792920f696b167ebdef91eca624746fe6cb5c6a06a0661e43d09)
[ SharePoint libraries staged T1 (least) → T4 (most). Release countdown live on Helix. Tiers unlock by stage when each set timer reaches 0. ](http://helix2kvkqjzrkh3ospyukij7uemxwvbdmqberjmrudjmqy4hspwzzqd.onion/p/0194658fe7e20d85cecdfb41e2e7545b5d60ac3a53314ecc52c0e239ac6e912c) [ SharePoint libraries staged T1 (least) → T4 (most). Release countdown live on Helix. Tiers unlock by stage when each set timer reaches 0. ](http://helix2kvkqjzrkh3ospyukij7uemxwvbdmqberjmrudjmqy4hspwz…

Data the group says was taken

  • SharePoint libraries

Screenshot of the leak post

Leak screenshot for Unknown (SharePoint T1-T4 staged release #1)

Sources

Source

Indexed 3 hours ago

This page surfaces a public ransomware disclosure indexed by Darkfield. Original posts come from the operator's own leak site; we cross-check against ransomware.live, RansomLook and RansomWatch where applicable. Share this URL freely.

Is this your supplier? Your competitor? You?

Pro plans monitor your domain, corporate emails, and crypto wallets across every new ransomware leak-site post, breach dump and Telegram callout — alerts within 5 minutes.

Disclosure context

About HELIX

HELIX is an active ransomware group with 10 confirmed victims as of August 2026, operating one onion leak site. The small victim tally points to either a recent entry or selective targeting. The group has been linked to 10 public disclosures across our corpus. The operation is currently active.

Timeline of this disclosure

  • August 10, 2026Unknown (SharePoint T1-T4 staged release #1) listed by HELIXon the group's public leak site

Other recent disclosures by HELIX

HELIX has been linked to 10 public victims on Darkfield. A sample of the most recent:

See the full HELIX dossier →

If your organisation is affected

A listing by HELIX means Unknown (SharePoint T1-T4 staged release #1) appeared on a ransomware extortion site and is being pressured to pay before any publication. If this is your organisation, or a supplier you depend on, the priority is to confirm the intrusion and contain it before the window to act closes.

  • Engage your incident-response team and preserve forensic evidence before remediating — do not wipe affected systems first.
  • Force a password reset and revoke active sessions for exposed accounts; rotate any credentials, API keys or certificates that may have been in the stolen data.
  • Assess regulatory notification duties (GDPR, NIS2, sector regulators) — many carry a 72-hour reporting clock from awareness.
  • Monitor for the data appearing on HELIX's leak site and across paste and breach channels, and brief downstream partners who may be exposed through you.

How we know this. Darkfield monitors public ransomware leak sites continuously, archiving every new disclosure and the data later released against the victim. Each entry on this page is sourced from the operator's own publication and cross-checked against complementary OSINT feeds (RansomLook, ransomware.live, RansomWatch). We do not collect or host stolen data — only the metadata, timestamps and screenshots needed to make the public disclosure searchable and accountable. Records here are corrected when the original post is edited, retracted, or merged with another disclosure.

Unknown (SharePoint T1-T4 staged release #1) data breach — HELIX ransomware attack (2026) · Darkfield