Parksite Inc.
bd_76535e8c523acc6f · schema v1 · pii pii-v1
Full breach record for Parksite Inc. →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Cactus 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
Post text · scraped from the leak site
Download link #1: https://***************.onion/PARKSITE/PROOFMirror: https://cactus5dqnqkppa5ayckiyk6dttpqwczdqphv5mxh4dkk5ct544q5aad.onion/PARKSITE/PROOF
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jan 17, 2024
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (9) · sorted by filing gap
- Vermont State AGbd_9935febd5a9e54712024-05-03 · +107dVerified by operator
- Illinois State AGbd_416f7923855228322024-06-01 · +136dVerified
- Massachusetts State AGbd_5391d639932e4d842024-06-07 · +142dVerified by operator
- Indiana State AGbd_65145629c8801aff2024-06-07 · +142dVerified
Show 5 more filings ↓Show fewer ↑up to 173d gap
- Maine State AGbd_da3ec50e6d994f572024-06-07 · +142dVerified
- New Hampshire State AGbd_f939f152fa41232f2024-06-10 · +145dVerified
- Vermont State AGbd_036c077381b65cce2024-07-02 · +167dVerified
- Maine State AGbd_63f500c0f7037c1c2024-07-02 · +167dVerified
- New Hampshire State AGbd_1da8b43afa323f452024-07-08 · +173dVerified by operator
Filing propagation · 10 filings · 6 states
View merged incident ↗Pattern: first filing Jan 17, last Jul 8 (NH) — a 173-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
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.
cactus
According to ransomware.live, The CACTUS ransomware is said to have emerged around March 2023. The group became known for exploiting vulnerabilities to gain initial access and maintain a presence within the organization's infrastructure. There is little known information about the ransomware group, except that it emerged on the mentioned date and, following encryption, a text file named 'cAcTuS.readme.txt' would be created. Additionally, encrypted files were altered to the '.cts1' extension, and data exfiltration and victim extortion were conducted through the use of the service known as Tox. Source: https://github.com/crocodyli/ThreatActors-TTPs