PRUDENTIAL FINANCIAL, INC.
bd_13768b7afb7253cc · schema v1 · pii pii-v1
Full breach record for PRUDENTIAL FINANCIAL, INC. →22 incidents on fileThreat-actor claim — not a regulatory filing
This row is a claim by the ransomware group ALPHV / BlackCat on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Feb 16, 2024
Claim posted
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (10) · sorted by filing gap
- Hawaii State AGbd_ae0d1296d328e7102024-03-01 · +13dVerified
- California State AGbd_36841bd9613d029d2024-03-29 · +41dVerified
- Massachusetts State AGbd_b1965b1a8cc9ac482024-03-29 · +41dVerified
- Maine State AGbd_eb8d330c9dcc702b2024-03-29 · +41dCandidate
Show 6 more filings ↓Show fewer ↑up to 97d gap
- Delaware State AGbd_f5ee337a95f0f5432024-03-29 · +41dVerified
- Maine State AGbd_b3527d1aa38e9c732024-04-01 · +44dVerified
- New Hampshire State AGbd_c86a2bebe35007342024-04-01 · +44dVerified
- South Carolina State AGbd_56760a94916f39a82024-04-23 · +66dVerified by operator
- Washington State AGbd_63338cbe564e28332024-04-23 · +66dVerified
- Oregon State AGbd_1b617c45cf572f7a2024-05-24 · +97dVerified
Showing first 10 of 12 linked disclosures.
Filing propagation · 10 filings · 9 states
View merged incident ↗Pattern: first filing Mar 1 (HI), last May 24 (OR) — a 84-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Cascade drawn from the first 10 linked disclosures of 12 — the full spread may be wider.
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
alphv
According to ransomware.live, The operators of the ALPHV/BlackCat ransomware began their activity in December 2021, making posts on Dark Web forums to promote their affiliate program, offering other actors the opportunity to engage in a 'new type of ransomware family' developed from scratch using the Rust programming language. Some clear evidence indicates that the actors behind this new ransomware are not new to cybercrime, and there were links to other affiliate programs such as DarkSide, BlackMatter, and REvil. (After several attacks against large companies, these groups faced pressure and arrests, necessitating the termination of their operations). As a security measure, the operators of ALPHV implemented the requirement for the execution of the ransomware payload by providing an 'access token,' which is supplied by the owners of the Ransomware-as-a-Service to the affiliate. This token is added to the victim's ransom note so that they can contact the threat actor responsible for encrypting the data. ALPHV affiliates employ double and triple extortion techniques, meaning the publication of the company's name on leak sites, threats of data leakage, and lastly, threats of DDoS attacks against the organization. Source: https://github.com/crocodyli/ThreatActors-TTPs