Go Strictly
bd_d3554889bd5877f5 · schema v1 · pii pii-v1
Full breach record for Go Strictly →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Akira 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
Go Strictly goal to help each of our customers make the most of t heir IT environments; whether managing and modernizing their curr ent systems or helping them incorporate new technologies. We are ready to upload some essentials corporate documents such a s: financial data (audits, payment details, reports), confidentia l licenses, agreements and contracts, HR documents, contact numbe rs and e-mail addresses of employees and customers, etc.
Source provenance
- Source URL
- https://www.ransomware.live/
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- Jan 2, 2025
- Raw hash
- 7a5817c6dc4eef2ba8ff1d449fd860976853a551d47c7f1048143fcf44090b3d
Reporting entity
- Name
- akira
Victim entity
- Name
- Go Strictlynorm: go strictly
- Domain
- gostrictly.com
- Industry
- Technologyllm
What this source establishes
- Source ceiling
- A leak-site claim can't tell us: discovery date · materiality · notification · affected count · confirmed data types · compliance clock. These stay blank until a regulatory filing or victim disclosure lands.
- Attack vector
- Ransomware· akira
- Threat actor
- AkiraExternalFinancial
Compliance
- Compliance flags
- — (clock not assessable for this source)
Extraction provenance
- Status
- No extraction artifact recorded for this disclosure.