Adaptavist Group LTD was listed on 23 March 2026 by the thegentlemen ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). thegentlemen listed 50 organizations that month and 1119 in total.
- Listed 242 days ago.
- 839 organizations were listed by all groups in March 2026, see the month.
- 144 in Technology that month.
- 33 in GB that month.
Updated 2026-11-19 05:47 UTC. Data: public leak-site listings. How we work.
Adaptavist Group LTD
Threat Group Post & Evidence
- Listed by
- Thegentlemen 1,119 listings in total
The listing states no data size and no ransom demand.
No capture of the original post
We only show a screenshot when we captured the group's own page ourselves. For this listing we have not, so none is shown.
What the group says it holds
Taken from the group's own post. Ransomware Tracker by ExposureDrift has not seen the data and cannot confirm any of this.
Adaptavist Group LTD is a British platinum Atlassian partner and enterprise software developer serving Fortune 500 clients including NASA, Visa, Deutsche Bank, and government organizations. The company's flagship product is ScriptRunner for Atlassian Jira, Confluence, and Bitbucket. Complete infrastructure compromise: source code of all products (ScriptRunner, Salable licensing platform), 484,220 customer records from HubSpot CRM (GDPR violation), 20,000+ legal tickets with 33,000 documents including 2,000 NDAs and contracts, 3TB+ from Nexus repositories (production secrets, Docker images, Helm charts), Kubernetes, OAuth credentials, Snowflake Data Warehouse, Confluence (24,547 pages, 100+GB documentation), production databases. Licensing system compromised enabling product cloning.
Amounts as written
- 500 clients
- 484,220 customer
- 33,000 documents
- 3TB
- 100+GB
Kinds of data mentioned
-
Passwords and credentials
“…repositories (production secrets, Docker images, Helm charts), Kubernetes, OAuth credentials, Snowflake Data Warehouse, Confluence (24,547 pages, 100+GB documentation), production databases.…”
-
Customer or client data
“…code of all products (ScriptRunner, Salable licensing platform), 484,220 customer records from HubSpot CRM (GDPR violation), 20,000+ legal tickets with 33,000 documents including…”
-
Contracts and legal files
“…platform), 484,220 customer records from HubSpot CRM (GDPR violation), 20,000+ legal tickets with 33,000 documents including 2,000 NDAs and contracts, 3TB+ from Nexus repositories…”
-
Source code and designs
“Complete infrastructure compromise: source code of all products (ScriptRunner, Salable licensing platform), 484,220 customer records from…”
-
Databases and backups
“…Warehouse, Confluence (24,547 pages, 100+GB documentation), production databases. Licensing system compromised enabling product cloning.”
Plain-English summary AI-written
The group says it holds product source code, customer records, legal tickets and documents, repository data, infrastructure credentials, and Confluence pages.
Written by an AI model (openai/gpt-6-luna) from the post above. It can contain mistakes: rely on the quote, not the summary.
What to do about this listing
Choose who you are. Each step shows why it appears and, where we have one, its source. General guidance, not legal or incident-response advice.
If you work with Adaptavist Group (customer, supplier or partner)
Within 3 days
- Do not open the group's page or download the data Do not visit the leak site or download files from a listing. Holding stolen data can be unlawful, and the files can carry malware. Wait for the company's own notice. Why: A safety rule for any leak listing.
- Ask Adaptavist Group directly Write to your contact and ask whether your data, or your access to their systems, is in scope, and ask for a written statement. Your contract or data-protection law may oblige them to tell you if your data is affected: check the notification clause. Why: A listing is only the group's claim; the company is the one who can confirm what was taken.
- Review what Adaptavist Group can reach of yours List the accounts, API keys, VPN or SSO connections and shared mailboxes this company has with you. Rotate the keys you gave them and remove access they do not need. Why: Access a supplier holds is how a listing about them can become a problem for you.
- Expect convincing phishing Messages that quote real orders, invoices or names are more likely after a leak. Tell finance and the help desk to treat any request from, or about, this company with extra care. Why: The post names: customer or client data, passwords and credentials.
- Check software and integrations you take from them If you run their software or call their API, check that updates come through the usual channel and rotate the keys and tokens you hold for it. Why: The post names: source code and designs, databases and backups.
Within 30 days
- Keep watching Adaptavist Group A supplier's listing can change after the first sighting: the group can add data, change the status or publish. Add the company to your supplier list to be told, and check your own domain too. Why: A listing is a moving claim, not a single event. Add to your supplier list Check your own domain
If you are Adaptavist Group
First 24 hours
- Reset credentials and sessions Force password, API-key and session-token resets for the accounts the post suggests were exposed, enforce phishing-resistant MFA, and revoke OAuth/SSO grants issued before the listing date. Why: The post names: passwords and credentials, customer or client data.
Within 3 days
- Rotate secrets and signing keys Assume secrets in repositories are exposed: rotate API keys, tokens and code-signing keys, and review build and release systems for unexpected changes. Why: The post names: source code and designs.
- Rotate database and cloud access Rotate database and cloud-storage keys, review public bucket and snapshot sharing, turn on object-level audit logging and keep backup encryption keys separate. Why: The post names: databases and backups.
- Size the exposure against your own systems Inventory which systems hold data of the kind and volume claimed, so notification and legal decisions rest on your records rather than the group's figures. Why: The post claims: 500 clients, 484,220 customer, 33,000 documents. Treat group figures as unverified.
- Lock down exposed admin, VPN and SSO panels Restrict by IP allow-list or a zero-trust proxy and require MFA. Why: A passive scan found 1 critical panel(s) reachable from the internet.
- Retire staging and dev exposure Take non-production hosts off the internet or behind authentication, and rotate any secrets they held. Why: A passive scan found 1 non-production host(s) that are public.
- Check regulatory and stakeholder notification duties United Kingdom: UK GDPR requires notifying the ICO within 72 hours of becoming aware of a reportable personal data breach. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: United Kingdom.
Within 30 days
- Review privileged and contract material Ask counsel which contracts and privileged files are named, and whether client or partner confidentiality terms oblige you to tell them. Why: The post names: contracts and legal files.
- Check shared suppliers and software List the suppliers and software you share with other Technology organizations and ask them whether they were affected. Why: thegentlemen listed 59 other Technology organization(s) in the last 90 days.
General readiness for any ransomware claim (not about this listing)
- Offline, immutable backups and a restore drill Keep backups outside domain-admin reach and practise a restore; a leak does not remove the risk of re-encryption. Why: General practice for any ransomware claim; not specific to this listing.
- Look for mass file access and unusual outbound transfers Review EDR, proxy and identity logs for bulk reads, archive creation and large uploads to file-sharing services. Why: General practice for any ransomware claim; not specific to this listing.
- Phishing-resistant MFA on remote access Enforce MFA on VPN, SSO and admin panels, and retire password-only or SMS-based remote access. Why: General practice for any ransomware claim; not specific to this listing.
Listing details
Listing severity score (heuristic)
88/100 • CRITICALA heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.
External Attack Surface Profile
ASM IntelligenceRun a free passive scan on your own domain to see what an attacker can see from the outside.