OPTICAL CABLE CORP
bd_ae0c0038bc213275 · schema v1 · pii pii-v1
Full breach record for OPTICAL CABLE CORP →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
Optical Cable Corporation ("OCC®") is a leading manufa cturer of the highest quality tight-buffer fiber optic cables and data communication connectivity solutions. Data is available to download. We have made the process of uploading company data as s imple as possible for our users. All you need is any to rrent client (like Vuze, Utorrent, qBittorrent or Trans mission to use magnet links). You will find the torrent file above. 1. Open uTorrent, or any another torrent client. 2. Add torrent file or paste the magnet URL to upload t he data safely. 3. Archives have no password. MAGNET URL: magnet:?xt=urn:btih:C24A0A93DF1AF21C1DA242D 1D7D65E9F087F496F&dn=occfiber.com&tr=udp://tracker.open bittorrent.com:80/announce&tr=udp://tracker.opentrackr. org:1337/announce&tr=wss://litetracker.world
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jul 30, 2023
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 (2) · sorted by filing gap
- Vermont State AGbd_938ca77ffc8b3c7d2023-07-05 · +25dVerified
- SEC 8-Kbd_3dcef407b0daff852023-06-30 · +30dVerified by operator
Filing propagation · 3 filings
View merged incident ↗Pattern: first filing Jun 30, last Jul 30 — a 30-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.
akira
According to ransomware.live, The Akira ransomware group is said to have emerged in March 2023, and there's much speculation about its ties to the former CONTI ransomware group. It's worth noting that with the end of CONTI's operation, several affiliates migrated to independent campaigns such as Royal, BlackBasta, and others. According to some reports, Akira affiliates also work with other ransomware operations, such as Snatch and BlackByte, as an open directory of tools used by an Akira operator was identified, which also had connections to the Snatch ransomware. The first version of the Akira ransomware was written in C++ and appended files with the '.akira' extension, creating a ransom note named 'akira_readme.txt,' partially based on the Conti V2 source code. However, on June 29, 2023, a decryptor for this version was reportedly released by Avast. Subsequently, a version was released that fixed the decryption flaw on July 2, 2023. Since then, the new version is said to be written in Rust, this time called 'megazord.exe,' and it changes the extension to '.powerranges' for encrypted files. Most of Akira's initial access vectors use brute-force attempts on Cisco VPN devices (which use single-factor authentication only). Additionally, exploitation of CVEs: CVE-2019-6693 and CVE-2022-40684 for initial access has been identified. Source: https://github.com/crocodyli/ThreatActors-TTPs