STEEL WAREHOUSE COMPANY LLC
bd_4a87e566495f86df · schema v1 · pii pii-v1
Full breach record for STEEL WAREHOUSE COMPANY LLC →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Cactus 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
<p>Steel Warehouse, founded in 1947 and headquartered in South Bend, Indiana, produces steel products. The Company offers panel flat, floor plate, hot rolled band, hot-rolled sheet, high strength low alloy, cold-rolled sheet, cold-rolled strip, and other steel products.<\/p><p>Website: <a href="https://www.steelwarehouse.com/">https://www.steelwarehouse.com/<\/a><\/p><p>Revenue : $570.3M<\/p><p>Address: 2722 Tucker Dr, South Bend, Indiana, 46619, United States<\/p><p>Phone Number: ([REDACTED-PHONE]<\/p><p><mark class="marker-yellow"><strong>Download link #1:<\/strong><\/mark> <a href="https://6wuivqgrv2g7brcwhjw5co3vligiqowpumzkcyebku7i2busrvlxnzid.onion/STEELWAREHOUSE/PROOF/">https://6wuivqgrv2g7brcwhjw5co3vligiqowpumzkcyebku7i2busrvlxnzid.onion/STEELWAREHOUSE/PROOF/<\/a><\/p><p><mark class="marker-yellow"><strong>Mirror:<\/strong><\/mark> <a href="https://cactus5dqnqkppa5ayckiyk6dttpqwczdqphv5mxh4dkk5ct544q5aad.onion/STEELWAREHOUSE/PROOF/">https://cactus5dqnqkppa5ayckiyk6dttpqwczdqphv5mxh4dkk5ct544q5aad.onion/STEELWAREHOUSE/PROOF/<\/a><\/p><p><mark class="marker-yellow"><strong>DATA DESCRIPTIONS:<\/strong><\/mark> Personal identifiable information, corporate confidential data, customer information, financials, employees\executives personal data, corporate correspondence, etc.<br><img src="/uploads/5_607d3554d8.png" alt="5.png"><img src="/uploads/4_f1c615f8e7.png" alt="4.png"><img src="/uploads/1_f29512f676.png" alt="1.png"><img src="/uploads/3_25b490b75d.png" alt="3.png"><img src="/uploads/2_ec6aea5c5f.png" alt="2.png"><\/p>
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Feb 6, 2025
Claim posted
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (6) · sorted by filing gap
- Indiana State AGbd_37ca52c9a8006bd42025-02-07 · +1dVerified by operator
- Nebraska State AGbd_7212e9d5181de2372026-03-24 · +411dVerified by operator
- Massachusetts State AGbd_3bc3002511614bea2026-04-30 · +448dVerified by operator
- Vermont State AGbd_de2712b90dea14442026-04-30 · +448dVerified by operator
Show 2 more filings ↓Show fewer ↑up to 476d gap
- Texas State AGbd_7a439add4d0e01c82026-05-01 · +449dVerified by operator
- Texas State AGbd_7ccc25d018b4b6c12026-05-28 · +476dVerified by operator
Filing propagation · 6 filings · 5 states
View merged incident ↗Pattern: first filing Feb 7 (IN), last May 28 (TX) — a 475-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.
cactus
According to ransomware.live, The CACTUS ransomware is said to have emerged around March 2023. The group became known for exploiting vulnerabilities to gain initial access and maintain a presence within the organization's infrastructure. There is little known information about the ransomware group, except that it emerged on the mentioned date and, following encryption, a text file named 'cAcTuS.readme.txt' would be created. Additionally, encrypted files were altered to the '.cts1' extension, and data exfiltration and victim extortion were conducted through the use of the service known as Tox. Source: https://github.com/crocodyli/ThreatActors-TTPs