Cargill Settles Class-Action Suit Over Kronos Ransomware Attack, Pays $2.4 Million to Employees

In a significant development, a federal judge approved a $2.4 million settlement on Wednesday for a class-action suit between food corporation Cargill and a group of current and former employees. The employees alleged that Cargill failed to pay them for all hours worked following the 2021 Kronos ransomware attack. The settlement, in the case of Futrell v. Cargill, comes after employees filed the suit in April 2022, citing pay discrepancies resulting from the Kronos attack on Cargill’s timekeeping and payroll systems.

Background

The Kronos ransomware attack caused widespread disruptions to Cargill’s operations, including its timekeeping and payroll systems. The impact of the attack resulted in significant pay discrepancies for employees, leading to the class-action suit. The suit specifically highlighted Cargill’s failure to pay non-exempt hourly workers and salaried employees their full overtime premium for overtime hours worked.

Allegations made in the lawsuit

According to the lawsuit, Cargill neglected to fully compensate employees for all hours worked, which is a violation of labor laws. The failure to pay overtime premiums to nonexempt hourly workers and salaried employees added to the grievances outlined in the suit.

Settlement terms

Under the terms of the settlement, Cargill has agreed to pay all underpaid collective members a proportional amount of the unpaid wages as liquidated damages. Additionally, nonexempt employees who worked in New York will receive an additional flat rate payment, while employees who were overpaid during the Kronos outage will also receive a per-person payment.

Ongoing fallout from the Kronos outage

Cargill is not the only employer facing litigation over its handling of the Kronos outage. The incident’s fallout continues to settle almost two years after the Kronos Private Cloud platform outage. In September, the University of Massachusetts Memorial Medical Center agreed to a $1.2 million settlement of wage-and-hour claims resulting from the breach. This ongoing litigation highlights the enduring impact of the Kronos attack on businesses and their employees.

Impact on HR departments

The Kronos outage created chaos for numerous HR departments, particularly during the critical 2021 holiday season. In the absence of functioning timekeeping and payroll systems, many HR departments had to resort to manual time sheets or duplicate payrolls from earlier pay periods to ensure workers could be paid on time. Such makeshift solutions further highlight the severe disruptions caused by the ransomware attack.

Employer Reactions and Future Use of Kronos

Despite the challenges posed by the Kronos attack, multiple employers interviewed after the incident expressed their intention to continue using Kronos and its parent company, UKG. Employers cited the company’s range of capabilities and the potential expense of finding an alternative as reasons for sticking with the system. The decision to remain with Kronos underscores the complex considerations involved in choosing and transitioning to a new platform.

Settlement by UKG

In addition to Cargill, UKG, the company that owns Kronos, also faced pressure to settle with affected employees. The outcome of this settlement is not explicitly mentioned in the current report, but it highlights the broader impact of the Kronos attack on businesses and their responsibility to address the grievances of their employees.

The $2.4 million settlement reached between Cargill and its employees is a significant milestone in addressing the pay discrepancies resulting from the Kronos ransomware attack. The case sheds light on the importance of safeguarding timekeeping and payroll systems against cyber threats to protect employee rights. As businesses increasingly rely on digital platforms, the incident serves as a reminder of the need for robust cybersecurity measures and proactive response strategies to mitigate the impact on employees and overall business operations.

Explore more

AI Rollouts Without Strategy Add Work and Erode Trust

Lead: The Moment the Promise Broke The moment a chatbot drafted the weekly report, the team exhaled—then spent the afternoon fixing tone, facts, and formulas the tool mangled while leadership called it progress. The calendar still brimmed with legacy checkpoints, yet new “AI review” steps quietly stacked on top. By dusk, what was sold as time saved had become time

No Excuses: How Leaders Build Accountability and Trust

Lead: The Moment an Excuse Lands Across a table or a screen, a single sentence—“Traffic was bad”—can slow a meeting’s pulse, dim a team’s energy, and quietly tell everyone that standards are optional when pressure mounts and outcomes wobble. Now contrast that with, “I’m late—and here’s how I’ll prevent it next time.” The second line resets momentum. It acknowledges the

Will BaaS Reinvent Credit Cards—or Raise Compliance Stakes?

Lead: A Hook Into Embedded Credit Pushbutton credit now hides inside shopping carts, travel feeds, and creator dashboards as Banking-as-a‑Service turns card issuance into an API, widening access while tightening scrutiny across every tap. A few lines of code can put a sleek credit card offer inside a checkout page, a loyalty wallet, or even a gig-worker earnings screen. The

Uganda Launches Postcom, a Postal-Powered E-Commerce Hub

Lead: Turning Counters Into Storefronts Shutters lift on a weekday morning, and what used to be just a mail counter begins doubling as a digital on-ramp where a boda courier tags outbound parcels, a clerk helps a crafts vendor upload product shots, and an order from a district away blinks on a screen with a promise of next-day delivery. The

Beyond Clicks: Resetting B2B Metrics for AI-Driven Buying

Lead: A New Power Struggle Over Credit Boardrooms are quietly celebrating fatter pipelines while dashboards flash red from falling clicks and vanishing form fills. The contradiction has become a weekly riddle: if top-line goals are met while web metrics sink, who or what deserves the credit? One quarter delivers fewer sessions and fewer MQLs, yet the sales team reports shorter