Analyst assessment
A cyberattack disrupted Sibanye-Stillwater’s information systems and delayed smelting and recycling at its Columbus metallurgical complex in Montana in July 2024. The company confirmed the processing delays and use of manual workarounds. Later notices warned of possible U.S. employee-data exposure, and the company’s annual filing subsequently confirmed unauthorized access to business and employee information. The incident is presumed resolved, with the exact end of disruption unverified.
Operational significance
MTN News reported computer outages on July 10. The report described the company’s subsequent statement that only payroll was affected, alongside a United Steelworkers official’s account that disabled automated systems had affected the Columbus smelter. Employees remained on the job.
The company’s July 11 announcement confirmed a global cyberattack and containment measures. Its July 25 update then acknowledged that IT outages delayed both smelting of underground concentrate and recycling of spent automotive catalysts at Columbus. It said mining and extraction continued globally with limited disruption. These findings establish a processing interruption without showing that every mine or the entire complex stopped operating.
The company said most systems were back by July 25, but anticipated a return to full Columbus operations and later processing of accumulated material. It also moved its half-year results announcement from Aug. 29 to Sept. 12.
In its Sept. 12 presentation, the company said the majority of its technology environment had been restored within three weeks. It described Montana stockpiles accumulated during July and August that would be processed later. Its third-quarter update subsequently linked the processing downtime to approximately 20,000 ounces of above-normal mine-concentrate inventory during that quarter. Planned year-end processing is not evidence of a completed backlog clearance, and the reviewed sources do not supply an exact restoration date.
Confidence and uncertainty
A Sept. 7 employee notice said the attack was discovered around July 8. Investigators identified indications of unauthorized activity on U.S. systems dating to mid-June; the notice did not give an exact initial-access date. Potentially affected employee files included contact and identity details, Social Security and tax identifiers, financial information and health-plan information. The company offered identity and credit monitoring.
In its 2024 annual filing, filed April 25, 2025, the company said an unauthorized party accessed business and personal information, mainly concerning current and former employees. It also reported restoring affected systems from available restore points and preserving critical enterprise-system data integrity. That recovery finding does not negate the separately disclosed access to personal information.
A July 22 Hackmanac post documented a RansomHouse listing alleging 1.2 terabytes of stolen data. Its attached claim image also alleged encryption and pressured management over threatened disclosure. These are claims, not independent findings about the attack’s method or data volume.
The company’s spokesperson had told Miningmx that no ransomware had been found at that early stage and the operator was unknown. Later reporting by The Record instead named RansomHub, conflicting with the contemporaneous RansomHouse observation. The reviewed company notices do not identify the operator. Responsibility, encryption and the claimed theft volume remain unverified.
A local MTN News report described a complaint filed Sept. 20, 2024, in Yellowstone County District Court by current and former employees alleging that the company failed to protect personal information. The report does not establish liability, class certification or a final outcome.
Analytic gaps
The exact restoration date, completion of the processing backlog and any ransom payment remain unverified. The annual filing’s discussion of recovered systems does not establish when every service returned or resolve the conflicting operator reports.