MAD OCTOPUS
GamesBlogDev HubCreator Hub
Back to Blog
August 31, 20268 min read

How We Ban Steam Key Farmers (and Why Real Creators Win)

Ten days ago we wrote about the week we went reseller hunting. This is the follow-up nobody planned: one weekend where the ban list grew past 460 addresses, 289 farmed keys went back to their developers as ready-to-revoke files, and we learned exactly where Steamworks hides its ban button. Here's how the pipeline works now - and why every farmer we cut means more keys for the creators who actually play indie games.

Piotr Karbowski

Founder, Mad Octopus

Share:XLinkedInBlueskyReddit
  1. 01The two-second tell
  2. 02We look at what a channel actually plays
  3. 03The library hoarders
  4. 04How to revoke farmed keys in Steamworks
  5. 05Why real creators win
  6. 06Devs: your claimer list has a ban hammer
  7. 07Two doors, both free to walk through

The two-second tell

A human who gets a key mail reads it, thinks about the game, maybe watches the trailer, and then claims. A scanner doesn't read anything. Our claim watch flags every account that claims keys from two different games within two seconds - a thing no person browsing their inbox has ever done. One recent morning it caught five addresses at once, holding 91 keys between them. All five are gone, their unclaimed links are dead, and their names sit on a do-not-send list that has now grown past 460 entries: grey-market resellers, curator farms, agency mailboxes, and plain old bots.

The point of the list isn't revenge, it's hygiene. Every address on it stops receiving key mails forever, so a developer's next campaign lands only in inboxes where a real person might press record.

We look at what a channel actually plays

Bots are the easy part. The hard part is the account that looks like a creator, claims like a creator, and never covers anything. For those we do the unglamorous thing: a human opens the channel. We pull the recent uploads, streams and clips and look at which games they actually come from - not the bio, not the follower count, the content.

The rule we settled on is simple. If a channel genuinely plays small indie games, it stays - even if it has never touched a single game from our catalog yet. A 150-follower streamer with honest VODs is exactly who these keys are for. What gets cut: channels that only ever stream AAA titles yet hoover up indie keys, agency mailboxes with no channel behind them, accounts with no content anywhere, and anything that claims by script. Borderline cases don't get auto-banned - they stay in a review queue until a human makes the call.

The library hoarders

Between the resellers and the real creators sits a third species. One studio went through the flagged keys we sent them and noticed that 5 of the 9 keys had been activated the same day they were claimed. That's not a reviewer with a backlog - that's someone padding a personal Steam library with free games they never intend to show anyone. No grey-market listing, no crime you can point at, and still zero value returned to the developer who paid for that key with a lost sale.

Hoarders get the fair-warning treatment we described in part one: show us anything you made, and "huge backlog, haven't gotten to it yet" counts as an honest answer. The ones who answer stay. The ones who go silent join the 460.

How to revoke farmed keys in Steamworks (the part that's easy to miss)

Cutting a farmer from our base kills their unclaimed links, but keys they already grabbed live on Steam - only the developer can kill those. So that's what we do now: when we ban an account, every key it took goes back to its developer as a ready-to-upload file. In one weekend that meant 289 keys mailed back to 14 studios. If you're a developer holding suspect keys from any source, here's the short version of what we learned:

  • Query CD Key won't ban anything. Steamworks' key lookup page shows a key's activation status, and that's all it does. There is no ban button on it. If you've been staring at it wondering where the hammer is - it's elsewhere.
  • Banning is batch-only. The actual tool is Steamworks' batch ban page (Store presence → your app → "Ban CD keys", or partner.steamgames.com/partnerbatchbancdkeys). It takes a plain .txt file, one key per line, and kills every unactivated key on the list in one upload.
  • Activated keys are a judgment call. The batch page can also revoke keys that were already redeemed - the user gets a notice from Steam and the game leaves their library. Our rule: revoke everything taken by bots and agency mailboxes, but leave activated keys with real streamers alone. The game is already in their library; a fraud notice there buys you nothing but anger.
  • Check status in bulk first. Our free Steam key checker takes a pasted list and tells you which keys are already activated and which are still live - through your own Steamworks account, keys never leave your browser.

One studio that ran this exact play told us the fraud notice was the point: a hoarder who grabs keys to pad their library gets a very educational message from Steam. We get it. Just aim it at the right people.

Why real creators win when farmers lose

Here's the part that makes the ban hammer worth swinging. Developers are not stupid: they stop handing out keys the moment keys stop turning into coverage. Every farmer we cut is the reason studios keep depositing fresh keys into the Creator Hub week after week - a catalog of 300+ indie games that 120+ vetted creators can claim from for free.

And because the base is clean, we can afford to be generous with the honest side of it. Approval is human and based on what you play, not how big you are - small channels welcome. Your first key per game is yours for the asking; extra keys unlock when your coverage lands, so creators who actually publish videos get more, not less. When a game you asked about gets restocked, you get a ping. Every key a farmer doesn't steal is a key that ends up in one of those inboxes instead.

Devs: your claimer list has a ban hammer attached

If you run a key campaign through the hub, your claimer list is not just a report - it's a weapon. Every row has the 👍/🚩 flags from part one, and confirmed bad actors now show a ⛔ banned chip right in your list, with a one-click download of their keys as a .txt file ready for the Steamworks batch ban page. One developer's report cuts the account from the entire base, not just their game. A thousand developers reading their own claimer lists remains the best fraud detector we know - so keep the reports coming.

Two doors, both free to walk through

If you make indie games: join the Dev Hub, add your game by its Steam link, and hand out keys knowing someone is watching where they go. If you cover indie games: apply to the Creator Hub, get approved by a human who will actually look at your channel, and claim from the whole catalog. The farmers can have the grey market. The keys are for you two.

Open the Dev HubJoin the Creator Hub

About Mad Octopus

Mad Octopus is an indie Steam publisher from Poland and the team behind the Mad Octopus Dev Hub, a free launch hub for Steam developers: bundle matchmaking with 400+ indie studios, curated creator key mailings with live dashboards, a free Steam page audit and a Creator Hub where human-vetted YouTubers and streamers claim keys. Founded by Piotr Karbowski (ex-CEO of CreativeForge Games). Free to join at madoctopus.fun/bundles.

MAD OCTOPUS

Indie Steam publisher helping developers publish and market games on Steam. Fair deals, aggressive marketing, zero BS. Founded by Piotr Karbowski, veteran of the gaming industry.

Steam Publishing

  • Steam Publishing Services
  • Free Resources
  • How to Publish on Steam
  • Published Games
  • Bundle Matchmaking
  • Blog
  • FAQ
  • Keymailer alternative

Connect

  • Submit Your Game
  • Discord
  • LinkedIn
  • X (Twitter)
  • YouTube
  • Follow us on Steam
  • Privacy Policy
  • Terms of Service

© 2026 Mad Octopus. Indie Steam publisher. All rights reserved. | Privacy Policy