Ransomware Tracker by ExposureDrift
Dashboard / Victims / Heng An Standard Life Insurance

Heng An Standard Life Insurance was listed on 21 March 2026 by the blacknevas ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach).

  • Listed 243 days ago.
  • 839 organizations were listed by all groups in March 2026, see the month.
  • 56 in Financial Services that month.

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

Heng An Standard Life Insurance corporate emblem
Listed by blacknevas Disclosed: 2026-04-30 23:17 UTC

Heng An Standard Life Insurance

hengansl.com.hk Financial Services HK

Threat Group Post & Evidence

Listed by
Blacknevas 47 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.

Downloaded:Complete Client Database: Unencrypted records containing full names, addresses, scanned identification documents (passports, driver’s licenses), and biometric facial data.Corporate Intellectual Property: All proprietary IT solutions, source code repositories, and internal development tools.Executive Correspondence: The complete archive of the Board of Directors meetings, including minutes, strategic plans, and the entirety of internal email correspondence among top management.We offer all data for purchase.The company's management concealed the fact of the leak.Heng An Standard Life Insurance is a major insurance company specializing in life insurance, operating primarily in the Asian region.

Kinds of data mentioned

  • Identity documents

    “…records containing full names, addresses, scanned identification documents (passports, driver’s licenses), and biometric facial data.Corporate Intellectual Property: All proprietary…”

  • Email and communications

    “…meetings, including minutes, strategic plans, and the entirety of internal email correspondence among top management.We offer all data for purchase.The company's management…”

  • Customer or client data

    “Downloaded:Complete Client Database: Unencrypted records containing full names, addresses, scanned identification documents…”

  • Source code and designs

    “…documents (passports, driver’s licenses), and biometric facial data.Corporate Intellectual Property: All proprietary IT solutions, source code repositories, and internal development tools.Executive…”

  • Databases and backups

    “Downloaded:Complete Client Database: Unencrypted records containing full names, addresses, scanned identification documents (passports,…”

Plain-English summary AI-written

The group says it holds client records with personal and biometric data, corporate intellectual property, and executive meeting minutes, plans, and emails.

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 Heng An Standard Life Insurance (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 Heng An Standard Life Insurance 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 Heng An Standard Life Insurance 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, email and communications, identity documents.
  • 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 Heng An Standard Life Insurance 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 Heng An Standard Life Insurance

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, email and communications, 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: 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.
  • 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.
  • Check for mailbox compromise Audit mailbox rules, forwarding and delegated access, rotate mail-admin credentials and move DMARC to p=reject to limit follow-on phishing. Why: The post names: email and communications.
  • 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.

Within 30 days

  • Check shared suppliers and software List the suppliers and software you share with other Financial Services organizations and ask them whether they were affected. Why: blacknevas listed 1 other Financial Services 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

Resolved Domain hengansl.com.hk
Industry Vertical Financial Services
Country HK
Enrichment Status ENRICHED

Listing severity score (heuristic)

56/100 • GUARDED

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 10/25 pts
Tier 3: all other groups
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
66/100 • HIGH
Last Audited: 2026-11-14 16:41 UTC Passive Recon
Total Network Assets 20
3 hosts • 17 unique IPs
0 cloud-hosted • 2 SaaS
Subdomain Assets 3
Critical Panels 0 (VPN/Admin/SSO)
Non-Prod / UAT 0 Staging/Dev
SaaS Ecosystem 2 Cloud Apps
Primary CSP Public Cloud / E
Email Security Grade B (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 Microsoft 365 / Exchange Online
DNS Authority Cloudflare Managed DNS
Edge CDN / Shield Cloudflare CDN / DDoS Shield
SPF Record Configured
DMARC Policy Enforced
Public DNS records only • no port scanning