A Used CPU Carrying Someone Else's Sentence — HWID Bans and the Crack in VALORANT's Trust

One August evening in Germany, a VALORANT player installed an AMD Ryzen 7 5800X3D chip into his motherboard. He had bought it on Kleinanzeigen, Germany's largest classifieds marketplace, where people sell used gear the way others sell vegetables at a market. He pressed the power button. The cooler spun. The RGB lights glowed. The operating system booted normally. Then he opened VALORANT and the screen told him his account was locked. Not because he aimed too well. Not because he had installed cheating software. But because the chip inside his machine had once lived in another machine, and that machine, according to his account, had been flagged by Vanguard.

I read this story on a night in Seoul, when the city had gone quiet and the coffee beside me had long gone cold. My first feeling was identical to the one I had standing in the Kazan stands in 2026: there was something in the movement the eye could not catch, but the ear could hear. In Kazan, it was the stride of Kim Young-gwon in that 92-metre run in the 90th-plus-third minute. Here, it is the rhythm of a ban running through a machine to reach someone who never did anything wrong. Every frame of film has a breath, and in Kazan that breath asked me a question — a question I have carried with me for more than a decade, only changing arenas.

And as always, I opened the archive before writing a single word.

What Vanguard is, and how an HWID ban differs from an ordinary account lock

To tell this story properly, I have to begin with the deepest layer of your computer: the operating system kernel. Vanguard is the anti-cheat software Riot Games installs alongside VALORANT. It does not run like an ordinary application. It runs at the kernel level — the core of the operating system, where software has the deepest access, where it can see almost everything happening on the machine: which processes are running, which drivers are loaded, which devices are connected. That is why Vanguard starts with Windows and stays on watch, even when you are not playing VALORANT.

The kernel is territory few programs dare to enter, because entering it means taking on both power and responsibility. Software at this layer can protect you from malware, but it can also see things you would rather no one saw. This is why Vanguard has long sat at the centre of privacy debates, and why, whenever it makes a decision, that decision carries unusual weight.

When an account is locked, that is punishment at the account level — you lose that account, create a new one, rebuy your skins, and move on. But when a machine is blacklisted, that is punishment at the hardware level. The technical term is HWID ban — Hardware ID ban. Instead of blocking only the account, the system flags the machine's hardware fingerprint: the CPU serial number, the motherboard identifier, the drive, the network card. The purpose is clear: to stop a banned cheater from simply creating a new account and coming back. Lock the account, and he switches accounts. Lock the whole machine, and he must buy a new one — or quit.

That is the logic of a defensive system. On paper, it is sound. But it has a blind spot, and that blind spot is the soul of today's story.

The specific case: August 12 and the chip that carried a sentence

According to an account that spread on Reddit and was later relayed by Kotaku and PCWorld, this German player bought the chip on Kleinanzeigen. On August 12, he discovered that the CPU's identifier or serial number had been blacklisted in Vanguard. He said Riot explained to him that the chip had previously belonged to a player who had cheated. In other words, his machine inherited the sentence of its previous owner.

There are three things here that must be separated clearly, because if we do not separate them, we turn a governance story into an emotional one — and emotion takes no one anywhere.

First, this story comes from a single source. It was self-published by the player on Reddit and then picked up by tech media. Riot Games has not confirmed it. This is the single most important point, and I will return to it repeatedly, because it determines how we should read the entire affair.

Second, PCWorld itself, in its reporting, described cases like this as rare. Rare. That is the base rate every serious analysis must place on the table before talking about a doomsday scenario.

Third, the mechanism behind the story is real. HWID bans are a real tool, operated in reality, not a product of imagination. So even if this specific story awaits verification, the framework it exposes cannot be waved away.

I walk into the archive as an archaeologist; when I leave, I am a storyteller. And what I found in the archive this time was not a match, but a transfer of power: power moving from the player's hands into those of an automated system, and that system cannot tell the difference between the person who committed the offence and the person who bought the offender's gear.

Collateral liability: when punishment lands on the innocent

This is the heart of the governance problem. In law there is a concept called collateral liability — when a punishment meant for an offender falls instead on someone else, someone who took no part in the offence. In this story, the buyer of the used chip is exactly that innocent third party. He bought a legal item, on a legal marketplace, and was stripped of his right to play by the actions of someone he had never met.

Picture a relay race. In relay, there is a moment called the exchange zone — the area where one runner hands the baton to the next. If the baton is marked, the receiving runner has done nothing wrong, yet can still be disqualified by the officials. An HWID ban works exactly the same way: the baton — the chip — is passed from hand to hand, but the mark travels with the baton, not with the person carrying it.

What makes the problem more serious is the power structure behind it. Riot here is simultaneously the lawmaker, the enforcer, and a party with a commercial stake in the game. No independent arbitration body stands in between to judge. In football, when a player is wrongly suspended, there is a disciplinary committee, a sports court, a published appeals process. In esports, that structure is still young, and much of it sits in the hands of the publisher itself. That is a structural feature, and it is precisely this structural feature that makes every Vanguard decision more sensitive than an ordinary account lock.

A hardware-linked ban turns a used component into an invisible debt the buyer cannot check before paying — and that is the problem, not the ending of one personal account.

The appeal gap: a remedy that exists on paper but is hard to win in practice

In any mature justice system, the part that matters as much as the verdict is the path of appeal. A system deserves trust only when the person punished can say: I was wronged, please review this. If that path is unclear, or exists but is hard to walk, trust in the system erodes from within, whether or not each individual verdict was correct.

This story shows a gap at exactly that point. The player's machine was locked, and the first question he must answer is: where do I appeal, how, and what evidence is enough to prove I am innocent? He must prove that the chip was not flagged because he cheated, but because of the previous owner. But how can he prove that? With a purchase receipt from Kleinanzeigen? With chat messages to the seller? Those are fragile pieces of evidence, and we have no documentation showing a standard process for receiving them.

This is the point I consider most important in the long run: the problem is not that one person's machine was locked, but that no one knows for certain how they would be vindicated if it happened to them.

One could argue: Riot has a support-ticket system, an appeal channel. True. But an appeal channel that exists is not the same as an appeal channel that is public and standardised. In football, when VAR arrived, the first demand was for a public process — when VAR intervenes, who decides, who is accountable. Not to make VAR perfect, but to let fans know the rules of the game. Here, the rules of the HWID ban have not been written for the public to read.

There is one small but telling detail in the account: other components in the system were also affected. This suggests Vanguard may have flagged multiple hardware fingerprints, not just a single serial number. If so, the scope of the ban is wider than it appears, and that makes the appeal question more urgent.

The used market and the problem of information asymmetry

Now let us leave the game screen and step into the market. Kleinanzeigen is one of Europe's largest secondhand marketplaces. People sell CPUs, GPUs, RAM, entire used computers. For a significant share of gamers — especially young ones on tight budgets — the used market is the door into PC gaming. You cannot afford a new chip, so you buy a used one. You cannot afford a whole rig, so you upgrade piece by piece.

An HWID ban touches that very door.

Economics has a concept called the lemons market. It describes a situation where buyers cannot assess the quality of goods before purchase, while sellers know clearly. The result is that buyers always suspect, pay low, and the market degrades. Here, the problem is subtler: the seller may also not know whether the chip is flagged by Vanguard. Both sides are blind, and the buyer bears the final consequence.

Try putting yourself in the buyer's position. You go to the market looking for a Ryzen 7 5800X3D — a chip gamers hunt for because of its strong price-to-performance. You look at the listing. You see the price. You see a few photos. You see no information about whether this chip was ever flagged by an anti-cheat system. There is no way to look it up. No mechanism to verify. You pay, take it home, install it, and you may — just may — have bought a machine that was locked before you even played your first match.

The cost of this mistake is not small. According to the account, the player may have to replace the entire computer, not just the chip. If true, this is economic harm at the level of a single consumer, not a club. But that individual harm, multiplied by the number of used-gear buyers, becomes a market problem.

The transfer market is loud, but I still hear the stride of a young talent falling silently. In esports, young talent often starts from cheap rigs, from used parts, from internet cafés or bedroom corners. If the used market becomes a little more frightening, the price is not paid by any giant, but by the kid who wants to start playing.

Manufacturer AMD has no obligation and no mechanism to disclose that a chip has been flagged by an anti-cheat system. Marketplace Kleinanzeigen is the same. No one in this supply chain is responsible for telling the buyer the truth, and so risk concentrates entirely on the weakest party in the chain.

Competitive integrity: when trust is placed on the scales

In sport, there is an intangible asset more precious than money: the belief that the game is fair. Fans spend money on tickets and jerseys and stay up late to watch because they believe the results are real, that no one is cheating, that if anyone cheats the system will handle it correctly. This belief is called competitive integrity.

A ban aimed at a cheater protects that belief. But a ban that accidentally strikes an innocent person erodes that same belief, in a different way. Players begin to ask: if the system can lock my machine for a reason I cannot control, how much can I still trust the system? Teams and organisations also need to believe that sanctions are applied consistently. When consistency is doubted, the whole ecosystem shudders.

In this case, no team and no professional player is named. The affected subject is an anonymous ranked player. That is why I do not tell this story as the story of a star. It is a systemic story, and its weight comes from creating a precedent about how a publisher treats a consumer.

There is one detail I want to make clear: in esports, when a pro's account is locked, the story is usually seen through the lens of personal image. When a used-gear buyer's machine is locked, the story is seen through the lens of money. Two different lenses, but both point to one place: the publisher's power over a player's digital life.

The counterintuitive angle: a rare event being inflated into a panic

Now I want to brake for a moment. Because after hearing enough calls for justice, a serious writer must ask: how big is this story, really?

The available evidence is one case. One. PCWorld, in its reporting, described such cases as rare. That means we have an edge case, not a spreading plague. The story was posted on Reddit, then picked up by Kotaku, then spread across tech sites. This circulation loop makes a single case look like a movement. That is the nature of digital media: a personal story moving enough can grow far larger than its statistical truth.

There is a trap writers on esports easily fall into, and I call it the hype trap. It happens when a singular, emotional, relatable case is generalised into a claim about the whole system: used PCs are now dangerous for VALORANT. That claim far exceeds the available data. And when a claim exceeds the data, it is no longer analysis; it is fear, packaged.

So what is genuinely worrying? In my view, the genuinely worrying thing is not the chip, but the opacity. A rare event can still cause great harm if it happens to the right person at the right moment, and if it has no clear resolution. A rare case with no appeal is more frightening than a common case with a transparent process. So my critique centres not on frequency, but on structure.

One more thing about context. Vanguard has long carried a bad reputation in privacy debates, because it runs at the kernel level and stays on watch. That means the community is already in a sensitive state. A new story landing in an already-sensitive community will spread faster and farther than its data base justifies. This is a psychological rule, not a technical one, and a writer must recognise it to avoid being swept along.

And I must repeat once more: Riot has not confirmed the story. That means we are analysing an unverified event, based on one person's account. That does not make the story meaningless — because the mechanism behind it is real — but it forces us to state our limits. I do not know for certain whether the previous owner cheated. I do not know for certain whether the ban was truly tied to the chip. I only know that if it is true, there is a gap that needs closing.

The transmission chain: from publisher to player's pocket, then to trust

To see the big picture, draw a transmission chain. At the upstream end is the publisher's anti-cheat policy. Midstream is the player base and the consumer hardware market. Downstream is the perception of competitive integrity and community trust.

When the upstream end issues a hardware-linked ban, the current flows down and touches the used market. The used market is a key supply channel for grassroots esports — for amateur events, for internet cafés, for newcomers. When this channel is disturbed, the effect does not arrive at once; it seeps down slowly, quietly, and hard to measure.

Then the current touches trust. Players begin to look at Vanguard with different eyes. Not hostile eyes, but wary ones. And wariness, in an ecosystem where the publisher is both lawmaker and judge, is an emotion worth listening to.

What is notable is that this mechanism is not unique to VALORANT. HWID bans appear in many titles using kernel-level anti-cheat. That means the problem here has cross-title reach — it can spread to other communities, and governance pressure can form at industry scale. If that happens, today's incident may be remembered as the first drop.

This is where I see an opportunity. If Riot — and then other publishers — publicly documents the appeal process for HWID bans, publishes the criteria for what gets flagged, and opens a channel for used-gear buyers to check for themselves, then a negative event could become a governance reform. In sports history, the biggest steps toward transparency are usually born from a scandal, not a conference. VAR was born from controversial mistakes. Goal-line technology was born from a ghost goal. Here, too, it could be so.

But this opportunity has an expiry date. If silence drags on, the story will harden into a prejudice, and prejudice is harder to remove than fact.

What to watch from here

There are several signals I will be watching, and I suggest readers watch them too.

First is Riot's official response. Silence or a statement will decide where the story goes. If Riot confirms and explains, the story may close within weeks. If Riot stays silent, it will drag on and harden.

Second is the number of similar cases. One case is rare. Two or three independent cases and the story changes nature, from an isolated incident to a system design flaw. That is the threshold I am waiting for.

Third is a policy change. If Riot publishes an appeal process or a whitelist for flagged hardware, that will signal the publisher choosing the transparent path.

Fourth is disclosure practice on marketplaces. If Kleinanzeigen or eBay introduces a standard requiring sellers to disclose hardware status, information asymmetry will fall.

Fifth is spillover to other titles. If communities of other kernel-level anti-cheat games speak up too, governance pressure will reach industry scale.

I walk into the archive as an archaeologist; when I leave, I am a storyteller. And this story reminds me why I chose this trade. Not to praise victories, but to listen to the smallest strides — the stride of a used chip passing through three pairs of hands, the stride of a buyer unknowingly inheriting another's sentence, the stride of a system learning to tell the offender apart from the machine.

Kazan is not just a defeat. It is a stride I have never stopped listening to. And today, in a different arena — the arena of rules and trust — I hear a similar stride again, except this time it does not come from a player's legs, but from the motherboard of a stranger.

What I believe

I believe a mature sport is measured not by how many cheaters it catches, but by the fairness it grants the innocent. Catching cheaters is the easy part; protecting the innocent is the hard part, and that hard part defines a system's value.

I believe a publisher's power, however necessary to keep the playing field clean, must come with accountability. A power with no appeal channel is an unbalanced power, and balance is always restored eventually — if not from within, then from without: through consumer law, through community pressure, through stories like today's.

I believe the used market, that humble door leading young gamers into PC gaming, deserves protection from invisible risks buyers cannot see. An esports scene whose entry door becomes frightening is one quietly narrowing its own talent pipeline.

And I believe this story of the used chip, however rare and unconfirmed, is still worth telling — not to sow fear, but to place on the table a question the whole industry will have to answer: when an innocent machine is punished, whose trust is the thing actually being locked?

Only when I stop running do I hear the song of the Kazan stands. And this time, pausing amid the headlines about a flagged chip, I hear another song — the song of used-gear buyers, of small players, of those with no voice in the publisher's meeting room, yet who bear the consequences of every decision made there. That song is not loud. But it runs steadily, and it has not stopped.