A administrative glitch in New Jersey just handed political partisans their dream talking point.
When New Jersey Governor Mikie Sherrill announced that a Motor Vehicle Commission software bug erroneously registered roughly 6,600 noncitizens to vote between June 2023 and June 2024, the reaction was immediate. Within hours, national headlines flared. Social media posts exploded with claims that noncitizens were stealing American elections.
Here's the truth behind the noise.
The software error was real. The vendor made a serious mistake. But the claim that this proves widespread, coordinated election theft is flat-out false. Out of 6.6 million registered voters in New Jersey, fewer than 400 of those mistakenly registered noncitizens actually cast a ballot over multiple election cycles. That represents about 0.009% of all votes cast in the state's 2024 general election.
If you're trying to figure out what actually happened, how the error occurred, and why the numbers floating around internet arguments don't add up, you're in the right place. Let's break down the mechanics, the data failures, and what this saga actually tells us about state election security.
What Really Happened in New Jersey
To understand how this mistake happened, you have to look at how motor vehicle departments process voter registration. Under motor-voter laws, when you apply for or renew a driver's license, the system asks whether you're a U.S. citizen and if you'd like to register to vote.
Between June 2023 and June 2024, under former Governor Phil Murphy's administration, a third-party software vendor installed a code update that contained a critical flaw. When noncitizen applicants explicitly checked "No" to the citizenship question, the system recorded their answer correctly in the DMV database. But when transmitting data files to the state election management system, the software ignored the negative response and processed them as eligible voter registrations anyway.
The applicants didn't lie. They didn't lie on official forms or trick election workers. They did exact opposite—they explicitly declared their noncitizen status on government paperwork. The state's automated backend software simply failed to respect their selection.
Governor Sherrill, who took office in January 2026, disclosed the glitch on July 21 after internal state audits caught the error. She immediately ordered the cancellation of those improper registrations, launched an investigation into the Motor Vehicle Commission, and announced the termination of the software vendor's contract.
System glitches happen in complex IT operations. They should be caught faster, fixed quicker, and audited constantly. But a coding bug isn't a shadow conspiracy.
The Numbers Behind the NJ Voter Roll Bug
The political spin around this issue relies on mixing up three distinct sets of numbers: people registered, people who voted, and the political affiliation of those involved.
First, roughly 6,600 noncitizens were mistakenly added to state voter rolls over a 12-month period. Most of these people likely received sample ballots or voter notification cards in the mail without ever asking for them.
Second, the vast majority of those 6,600 people did the right thing. They ignored the voting materials or recognized they weren't eligible, and stayed away from the polls. Preliminary state audits show that fewer than 400 individuals cast a ballot in any election between 2023 and 2026.
Third, political commentators immediately claimed these voters were part of a partisan scheme to help one party. But state election records show those 400 individuals were registered across the entire spectrum. They were Democrats, Republicans, and unaffiliated voters scattered across various counties. There was zero pattern of targeted, organized voter packing.
When a noncitizen votes, even by accident after receiving an official state voter card, they face life-altering penalties. Federal law treats illegal voting by a noncitizen as a serious offense that carries prison time and mandatory deportation. The idea that hundreds of noncitizens would intentionally risk deportation just to cast a single ballot in a routine election defies basic common sense.
How DHS Data Distorts the Real Picture
While New Jersey was working to clean up its voter rolls, the federal Department of Homeland Security stepped into the fray with far larger numbers.
In a primetime address, President Donald Trump cited DHS figures claiming that over 278,000 noncitizens were registered to vote across four states: New Jersey, California, Nevada, and Pennsylvania. On Truth Social, claims surfaced that New Jersey alone had over 35,000 noncitizen voters on its rolls. Homeland Security Secretary Markwayne Mullin subsequently sent letters demanding that these states review their records within two weeks.
Where did the federal government get these massive figures?
They didn't get them from state voter registration files. Instead, DHS ran a federal database match using the Systematic Alien Verification for Entitlements system, commonly known as SAVE.
Election administration experts, including David Becker from the Center for Election Innovation & Research and Professor Charles Stewart III from MIT, have repeatedly pointed out why using SAVE for voter roll checks creates huge numbers of false positives.
The SAVE database was designed to verify eligibility for government welfare benefits, not to audit state voter files. Public voter records contain basic information: names, addresses, and birth dates. They do not contain sensitive government identifiers like Social Security numbers, Alien Registration Numbers, or naturalization certificate codes.
When DHS attempts to match public voter rolls against immigration records without those unique identifiers, the system generates massive numbers of false matches. Two people with the same name and birth date—one a naturalized citizen, one a temporary visa holder—get flagged as the same person.
Even in letters sent to state election directors, DHS conceded that out of its claimed 278,000 suspicious records, it could only attempt partial matches for about 118,000. It provided zero explanation or evidence for the remaining 160,000 names.
State election officials from both parties, including Nevada Secretary of State Cisco Aguilar and California Secretary of State Shirley Weber, quickly pushed back. They noted that federal agencies lack the granular, daily data that state election offices use to maintain accurate rolls.
State Power vs Federal Interference in Elections
Under the U.S. Constitution, states hold primary authority over how elections are organized and conducted. That separation exists for a reason. It prevents whatever political party controls the White House from manipulating local voting lists.
When federal agencies release unverified, broad database queries right before an election cycle, it creates massive administrative headaches for local clerks.
Cleaning voter rolls requires surgical precision. State law dictates strict procedural steps before removing anyone from the voter rolls. If a county clerk blindly wipes thousands of names off the voter list based on flawed federal matching, legitimate American citizens get disenfranchised.
We've seen this happen before. States that rushed to purge voter rolls using crude federal database comparisons ended up removing legal, naturalized citizens who shared common names with noncitizens.
The New Jersey incident shows the system eventually caught its own administrative failure. The state discovered the vendor bug, announced the findings publicly, corrected the registration records, and fired the contractor. That is how administrative oversight is supposed to work.
Weaponizing administrative errors to claim an entire electoral system is compromised harms public trust. It turns mundane IT bugs into political warfare.
What States Must Do to Prevent Future Software Failures
While the political rhetoric is wildly overblown, the New Jersey incident exposes real vulnerabilities in how state agencies handle IT contracting and automated registration systems.
State governments rely heavily on private vendors to write code for DMV and election databases. When those vendors push software updates without rigorous end-to-end testing, mistakes slip through.
Here are the concrete steps states need to take to keep their voter rolls accurate without disenfranchising legitimate voters:
- Mandate Strict Vendor Code Audits: Third-party software companies managing government databases must undergo independent code reviews whenever automated voter registration logic is modified. A simple automated test script would have flagged that checking "No" to citizenship was still creating a voter record.
- Implement Multi-Layer Logic Checks: State election systems should automatically reject any registration file from a DMV where the citizenship box is marked negative. Relying entirely on the transmitting agency's software to filter records creates a single point of failure.
- Conduct Regular Cross-Agency Audits: Instead of waiting for annual reviews, state election directors should run monthly cross-checks between DMV transaction logs and voter intake lists to catch anomalies before election deadlines.
- Demand Federal Transparency on SAVE Data: If federal agencies want to assist states with voter list maintenance, they must share full methodologies, error rates, and underlying data matches rather than issuing raw estimates without context.
- Protect Naturalized Citizens: Any voter roll maintenance routine must include clear notification periods allowing citizens to confirm their status before any registration is canceled or flagged.
Administrative errors in government software aren't grand conspiracies, but they are unacceptable operational failures. Fixing them requires competent technical management, better vendor oversight, and transparent public reporting—not partisan fearmongering.
