Pricon Microelectronics, Inc.
bd_817415c4af95e61c · schema v1 · pii pii-v1
Full breach record for Pricon Microelectronics, Inc. →Press / market disclosure — not a breach-notification filing
A media or market posting that confirms an incident but carries no breach-notification fields, so compliance clocks aren't assessable. The summary below is extracted from the coverage and machine-translated to English — verify against the source.
Summary
machine-translatedYamai Electric: Ransomware attack on Philippine subsidiary, logs encrypted and deleted, full identification of initial intrusion vector not achieved | ScanNetSecurity. Pricon Microelectronics: Yamai Electric Co., Ltd., a company listed on the Tokyo Stock Exchange, has published a final report regarding the ransomware incident at its Philippine subsidiary, Pricon Microelectronics, Inc. The attack, detected on April 17, affected certain servers. Although data was lost on some terminals, recovery was performed using backups, and operations were not severely disrupted. Investigations revealed no external data leakage, even though customer, partner, and employee personal information was stored on the affected systems. The subsidiary completed restoration on April 29, and all systems are now operating normally. Yamai Electric has implemented several countermeasures to prevent recurrence, such as introducing EDR and strengthening access management. The attack was claimed by the LockBit5 group on April 29. Linked ransomware group: lockbit5.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jun 17, 2026
Press report
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Attack → press
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Ransomware claims (2)
- Leak Sitelockbit5bd_dd3725779840dd8f2026-04-27 · +51dCandidate
- Leak Sitelockbit5bd_3905fe8a7b3bd2f02026-04-17 · +61dCandidate
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
- incident type + narrative only (may be machine-translated)
- discovery date
- materiality
- affected count
- data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
lockbit5
According to ransomware.live, LockBit 5.0 ("ChuongDong") emerged in September 2025 as the group's resurgence following the February 2024 law enforcement takedown, introducing cross-platform payloads targeting Windows, Linux, and VMware ESXi with enhanced evasion capabilities and continuing the RaaS affiliate model of its predecessors.