Loongson
bd_78d724641bbadb57 · schema v1 · pii pii-v1
Full breach record for Loongson →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group 8base 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
Loongson Technology keeps pace with international trends in the field of IT and focuses on the development of the industry and the construction of systems based on independent innovations. Until now, we have mastered the basic computing technologies in the field of designing the architecture of the processor instruction set (ISA) (LoongArch®), the IP core of the processor and the operating system. Based on this, they strive to create an independent and open hardware and software ecosystem and information industry system to provide independently developed, secure and reliable processors to meet national strategic needs, as well as high-performance, low-cost processors and basic software and hardware solutions to stimulate innovative development. But they could not protect their confidential data.https://www.loongson.cn/EN
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jun 19, 2023
Claim posted
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
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.
No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.
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.
8base
According to ransomware.live, The 8base Ransomware group made its first appearance in early March 2022, remaining somewhat quiet after the attacks. This group operates like other ransomware actors, engaging in double extortion. However, in mid-May and June 2023, the ransomware operation saw a spike in activity against organizations from various sectors, listing 131 organizations in just 3 months. The 8base data leak site was created and made available in March 2023, claiming honesty and simplicity in its discourse. VMware published a report on 8base, drawing some similarities with the ransomware group `RansomHouse`, pointing out resemblances such as the website used by 8base and the ransom notes presented in its attacks. Interestingly, the 8base Ransomware group does not have its own ransomware developed by the group. Instead, the actors took advantage of other leaked ransomware builders to customize the ransom note and present it to the victim organization as 8base's operation. Source : https://github.com/crocodyli/ThreatActors-TTPs