SUMITOMO BAKELITE
bd_a0237dae209a7246 · schema v1 · pii pii-v1
Full breach record for SUMITOMO BAKELITE →Threat-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
Post text · scraped from the leak site
Among the various plastics, phenolic resin has the oldest history. It was developed by Dr. Leo H. Baekeland, an American of Belgian ancestry, in 1907 and he named that synthetic resin "Bakelite". In 1911, Sankyo Company (currently Daiichi Sankyo Co., Ltd.) was assigned the rights to execute the patents in Japan through the good offices of Dr. Jokichi Takamine, a close friend of Dr. Baekeland. Trial production of phenolic resin was started at the Shinagawa Plant of Sankyo Company. That was the origin of the Japan's plastics industry, and the name of our company came from this achievement. In 1932, phenolic resin business of Sankyo Co., Ltd. was separated and formed Nippon Bakelite Co., Ltd. In 1955, Nippon Bakelite Co., Ltd. merged with Sumitomo Synthetic Resin Industries, Ltd. to found Sumitomo Bakelite Co., Ltd. As a pioneer in plastics, with our expertise in and up-to-date facilities for plastics, we have been always developing new technologies for use in various fields in order to contribute to establishing safe and comfortable living.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Oct 27, 2022
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.
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