Ransomware Tracker by ExposureDrift
Dashboard / Victims / AQIPA

AQIPA was listed on 29 November 2023 by the alphv ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). alphv listed 52 organizations that month and 717 in total.

  • Listed 1086 days ago.
  • 495 organizations were listed by all groups in November 2023, see the month.
  • 95 in Professional Services that month.

Updated 2026-11-19 06:42 UTC. Data: public leak-site listings. How we work.

AQIPA corporate emblem
Listed by alphv Disclosed: 2023-11-29 17:29 UTC

AQIPA

aqipa.com Professional Services

Threat Group Post & Evidence

Listed by
ALPHV / BlackCat 717 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.

The group's leak-site address is on paid plans

Free accounts see who listed this organization, when, and what the post claims. The address of the group's own page is shown to license-key holders. If you have a key, see what a license key adds.

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.

As a result of an attack on the corporate network of AQIPA.com, we obtained hundreds of gigabytes of data: - trade secret information (NDAs, lists of clients with full information about them, current and future projects of the company, development strategies and plans) - personal data of employees and clients (passports, insurance, driver's licenses; login data for personal accounts, social networks and messengers, etc.); - information disclosing the peculiarities of operation - non-public reporting documents concerning finance, management, HR, etc.

Kinds of data mentioned

  • Identity documents

    “…development strategies and plans) - personal data of employees and clients (passports, insurance, driver's licenses; login data for personal accounts, social networks and messengers,…”

  • Customer or client data

    “…hundreds of gigabytes of data: - trade secret information (NDAs, lists of clients with full information about them, current and future projects of the company, development…”

  • Employee and HR records

    “…projects of the company, development strategies and plans) - personal data of employees and clients (passports, insurance, driver's licenses; login data for personal accounts, social…”

  • Contracts and legal files

    “…we obtained hundreds of gigabytes of data: - trade secret information (NDAs, lists of clients with full information about them, current and future projects of the company,…”

  • Source code and designs

    “…corporate network of AQIPA.com, we obtained hundreds of gigabytes of data: - trade secret information (NDAs, lists of clients with full information about them, current and future projects…”

Plain-English summary AI-written

The group says it holds hundreds of gigabytes of company data, including trade secrets, personal information, and non-public finance, management, and HR documents.

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 AQIPA (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 AQIPA 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 AQIPA 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, identity documents, employee and hr records.
  • 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.

Within 30 days

  • Keep watching AQIPA 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 AQIPA

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: identity documents, customer or client data.

Within 3 days

  • Support affected individuals Identify the employees or customers whose identity data may be in scope and offer identity-protection or credit monitoring; brief the help desk on likely phishing. Why: The post names: employee and hr records, identity documents.
  • 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.
  • 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 2 critical panel(s) reachable from the internet.
  • Check regulatory and stakeholder notification duties No country is recorded for this listing. Identify the data-protection and contractual duties that apply where the affected people live, and ask counsel. General guidance, not legal advice. Why: The listing records no country.
  • Check the ways alphv is reported to get in Check these first; they are how the group is reported to work in general.
    • Affiliates impersonate IT or help-desk staff by phone or SMS to obtain credentials, and use the Evilginx2 framework to capture MFA codes and session cookies. (update of Feb 2024)
    Source: #StopRansomware: ALPHV Blackcat (AA23-353A) Why: From the public advisory below. It describes the group, not how AQIPA was entered.

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.
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

Resolved Domain aqipa.com
Industry Vertical Professional Services
Country Not stated
Enrichment Status ENRICHED

Listing severity score (heuristic)

75/100 • ELEVATED

A heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.

1. Sector Criticality 10/30 pts
Commercial and general business
2. Group tier 25/25 pts
Tier 1: among the groups with the most listings in our data
3. Data Volume & PII Scope 25/25 pts
Largest claim: a terabyte or more, or regulated data named in the post
Formula: sector • group tier • data claimed (scaled to 100) Rule-based score

External Attack Surface Profile

ASM Intelligence
88/100 • CRITICAL
Last Audited: 2026-11-14 19:17 UTC Passive Recon
Total Network Assets 19
6 hosts • 13 unique IPs
1 cloud-hosted • 4 SaaS
Subdomain Assets 6
Critical Panels 2 (VPN/Admin/SSO)
Non-Prod / UAT 0 Staging/Dev
SaaS Ecosystem 4 Cloud Apps
Primary CSP Public Cloud / E
Email Security Grade A (SPF/DMARC)
Open the full attack surface scan →
Is Your Organization Exposed?

Run a free passive scan on your own domain to see what an attacker can see from the outside.

Defense Telemetry

Passive DNS
Mail Gateway Mimecast Secure Gateway
DNS Authority Authoritative DNS (net)
Edge CDN / Shield None
SPF Record Configured
DMARC Policy Enforced
Public DNS records only • no port scanning

More Claims by alphv

All →
ipmaltamira
Professional Services 2024-03-03 16:14 UTC
Ewig Usa
Manufacturing 2024-03-03 02:51 UTC
SBM & Co
Professional Services 2024-03-01 22:16 UTC
Petrus Resources Ltd
Energy & Utilities 2024-03-01 19:06 UTC
Kumagai Gumi Group
Professional Services 2024-03-01 11:42 UTC
Allan Berger & Associates
Professional Services 2024-02-29 20:41 UTC