It began with a simple act of defiance: a lunch break. For Victoria Cox, a former sergeant with Metropolitan Protective Services (MPS) in Baltimore, the decision to eat her sandwich in her car during a 16-hour shift became a flashpoint in a larger battle over workers’ rights. Days later, she found herself under investigation, her shifts stripped from the schedule, and her job effectively revoked without formal termination. “They were going after everyone,” she said, her voice trembling with frustration. “It wasn’t just me. It was every single person who stood up for something better.”
Cox’s story is not an isolated incident. This proves part of a growing pattern of retaliation against workers who dare to organize, a trend that has ignited a national conversation about labor rights, corporate accountability, and the thin line between lawful protest and workplace punishment. In Baltimore, a city already grappling with economic inequality and systemic underinvestment, the conflict between security officers and their employer has become a microcosm of a broader struggle—one that pits the rights of workers against the power of corporate interests.
The strike, which began on April 9, 2026, was the culmination of years of frustration. Security officers at MPS, a contractor for the Baltimore Housing Authority and other city agencies, had long complained about low wages, lack of benefits, and unsafe working conditions. Many worked 12- to 16-hour shifts with no overtime pay, often patrolling high-risk areas like public housing developments and police stations. “We were the first on the scene in shootings, domestic violence incidents, and break-ins,” said Daril Riley, a former corporal with MPS. “But we were treated like disposable labor.”
The workers’ decision to unionize under SEIU Local 32BJ was met with immediate resistance. According to the union, MPS officials allegedly pressured employees to abandon the strike, threatened to cut paychecks, and implemented new rules designed to punish those who participated. “They started changing the rules daily,” Riley said. “One day, we couldn’t eat lunch in our cars. The next, we couldn’t lock the doors. It was like they were trying to make us quit.”
MPS has denied these allegations, stating that no employees were fired for union activity. “We fully support our employees’ right to choose whether or not to join a union,” said CEO Derrick Parks in a statement. “The individuals removed from the schedule were terminated for failing to maintain their Maryland guard licenses or for performance issues.” The company claims only six of its 175 employees have been let go, all due to “licensing or performance concerns.”
But for Cox and Riley, the timeline of events suggests a different narrative. The strike began on April 9, and by mid-May, both were under investigation. Cox’s offense? Eating lunch in her car. Riley’s? A disputed incident involving a security protocol. “They found a way to punish us for everything,” he said. “It’s not about the rules. It’s about sending a message.”
This pattern of retaliation is not unique to Baltimore. A 2023 report by the Economic Policy Institute found that 60% of workers who attempted to unionize faced some form of employer retaliation, including pay cuts, demotions, and wrongful termination. “Companies often use vague policies or ‘performance issues’ as a cover to silence dissent,” said Dr. Laura Gómez, a labor economist at the University of Maryland. “What’s happening here is a textbook example of how employers can exploit legal loopholes to undermine collective action.”
The legal landscape is murky. While the National Labor Relations Act (NLRA) prohibits employers from retaliating against workers for engaging in “protected concerted activity,” enforcement is often slow and inconsistent. “The NLRB is underfunded and understaffed,” said Michael Smith, an labor law attorney with the Workers’ Rights Project. “By the time a case is resolved, the damage is already done. Workers like Victoria and Daril are left in limbo, without pay, without benefits, and without a clear path to justice.”
For the workers, the financial toll has been devastating. Cox, who had recently bought a car, now faces mounting bills and uncertainty. “I don’t know if I’ll ever get my job back,” she said. “But I also don’t know if I can stop fighting.” Riley, a father of two, has been forced to rely on family support to make ends meet. “It’s not just about the money,” he said. “It’s about dignity. We didn’t do anything wrong. We just wanted to be treated like human beings.”
The union has not been silent. SEIU Local 32BJ has filed unfair labor practice charges with the NLRB and is pushing for state-level reforms to strengthen protections for workers. “This isn’t just about these two individuals,” said Jaime Contreras, an SEIU representative. “It’s about the right of every worker to organize without fear of retaliation. If we don’t stand up for them, who will?”
But the fight is far from over. As the investigation into Cox and Riley drags on, the broader implications for labor rights in Maryland—and beyond—remain unclear. For now, the workers are left waiting, their lives on hold, their futures uncertain. “We’re not giving up,” Cox said. “We’ve come too far. This isn’t just our battle. It’s everyone’s.”
For readers, the story of Baltimore’s security officers is a reminder of the power of collective action—and the risks that come with it. As the city’s workers continue their struggle, one question lingers: Will the system finally recognize their right to fair treatment, or will they be another chapter in the long, unresolved story of labor oppression?
Baltimore Sun: “Baltimore Contract Security Officers at City Properties Prepare to Strike”
