Story

Humble Bundle 2FA vanished in a 'vibe-coded' redesign: what builders shipping with AI should check

On 11 November 2026, Pirate Software posted that Humble Bundle 2FA was no longer prompted at login, and that the option to add or remove it was missing from account settings. The next day PC Gamer reported that people who already had that second factor on could sign in with an email and a password.

The post says: “Humble Bundle is suddenly not prompting for 2FA at login. The option to add or remove 2FA is also missing from account settings.” A follow-up the same day says: “You no longer have 2FA in your login flow and 2FA doesn’t appear anywhere in your settings.” PrivacyAffairs describes that account as run by game developer Jason Hall. Kotaku, Aftermath, Neowin, and a Hacker News thread carried the same gap the next day. The thread blamed the new site on vibe coding.

At the time of writing, Humble and owner Ziff Davis had not published a statement; some users, including Pirate Software, reported an email check returning, which is unconfirmed.

Indie game developers sell through Humble Bundle. Buyers keep libraries of keys in the same accounts. A login change on that store is a shopper story and a seller story.

What happened to Humble Bundle 2FA

The public record is a short calendar, and Humble had not published an account of its own.

When What is on the record
Summer 2026 Ziff Davis laid off Humble engineers. Workers told Aftermath in June that only two remained.
Before the public launch Ziff Davis told investors a relaunch was days away. Shah said the old platform hurt conversions.
11 November 2026 Pirate Software posts that 2FA is gone from login and from settings. Jankified: Humble is silent.
12 November 2026 Hacker News, PC Gamer, Kotaku, Aftermath, PrivacyAffairs, and Neowin.
12–13 November 2026 Reports of an email check returning. No public statement from Humble or Ziff Davis.

The layoffs and the June headcount are in Riley MacLeod's Aftermath piece of 12 November 2026. The investor line and the CEO line are in Miklos Zoltan's PrivacyAffairs report, also 12 November. The 11 November posts are Pirate Software and Jankified. The 12 November cluster is linked in the sections below.

The company’s stated reason for a new site was already public, and it is about sales. PrivacyAffairs says Ziff Davis told investors the relaunch was “days away”, and quotes CEO Vivek Shah saying the old platform “interfered with conversions and customer experience”. That sentence explains a relaunch. It says nothing about the login screen people met this week.

Did Humble Bundle remove 2FA?

Reporters described a missing prompt and a missing setting. Humble had not posted that the feature was being retired.

Joshua Wolens at PC Gamer, on 12 November, reported no 2FA support. People who had turned it on could log in with an email and a password. The FAQ still encouraged 2FA. Wolens wrote that PC Gamer had reached out to Humble. The piece recommends removing saved payment details. It quotes a post on r/humblebundle: “This is insanely bad, they need to take down password changes entirely until this is fixed”.

On the Hacker News thread, xavdid wrote: “I could log in without needing my 2FA at all.”

PrivacyAffairs described the new sign-in as a password, an emailed one-time code, or Google. The emailed code, in that report, is an alternative way in. The new auth on auth.humblebundle.com uses Ory, which can do 2FA. On whether that support is active, the report says: “It isn’t turned on”. The same report says the settings code still contains the hidden words “Two-Step Verification”. The old arrangement was a Google Authenticator two-step, plus “Humble Guard”, an emailed code when a new device signed in.

Humble’s support article on two-step verification was still up, describing the control reporters could not find in settings. PC Gamer’s note that the FAQ still encouraged 2FA is the same kind of mismatch. The help centre and the product had come apart.

Alicia Haddick at Kotaku, also 12 November, wrote that the trouble was first spotted on Reddit, on “what appears to be an all-new vibe-coded redesign”. Kotaku reported no extra check when changing a password. An email change, the piece says, verified only the new address. “We’ve tested this too”. The labels that separated redeemed keys from unredeemed keys were gone. There was no stay-logged-in option. Kotaku asked Humble, which the piece describes as owned by IGN, for comment.

Pirate Software put the ordinary point of a second factor in one line: “2FA stops attackers from getting in even if they do have that password.”

Was the new Humble Bundle site vibe coded?

Nothing public proves the new site was vibe-coded.

Aftermath’s phrase is “While there’s no proof of that”. PrivacyAffairs’ phrase is “Nothing public shows that”. On Hacker News, brindleth wrote that the article does not “provide any direct proof the new site was vibecoded”, and that “accusations like this are, ironically, just vibes-based.”

The accusation travelled anyway. Kotaku used the hedged line above. The Hacker News thread, posted on 12 November, is titled “Humble Bundle just killed most of their security through vibecoding”. It stood at 349 points and 213 comments. The submission links a SpaceBattles thread under a similar title. Aftermath, PrivacyAffairs, and brindleth each say the public record does not prove the method.

People reached for a thin team, and Aftermath put a date on that claim. Ziff Davis laid off Humble engineers over the summer. Workers speaking to Aftermath in June said only two engineers remained at Humble. That June report does not say who wrote the November site, or which tools they used.

Shah’s line, quoted above, is the reason Ziff Davis has put in public: conversions and customer experience, with investors told the relaunch was days away. A business reason for a new storefront can sit beside a weaker login. It leaves the author of the code unnamed.

The comments ran in several directions.

xx__yy wrote: “AI doesn’t produce bad software, people do.”

trvz wrote: “This is not AI’s fault.” The same comment called an emailed code at every login a pain. origini was glad 2FA was gone. Those two are readers who did not want the check. That is a separate argument from how the page was built.

oliwarner wrote about asking for auth systems several times: “they’ve tended to come with pretty good feature-sets. Perhaps it’s because I know what I’m asking for.” dtech would expect any model to require the old password by default. pona-a wrote that comment sections swing anti-AI with every vibe-coding disaster.

The comments that name a review are blunter. midasz wrote: “Even asking Claude to go through the site and note down things that don’t make sense would’ve prevented at least some of this.” u2secured_team wrote that “vibecoding required more guard rails and also human checks.” sinbadbuilds asked why the result was not checked “from a security pov” before launch.

The wider fight is already on the record, including whether vibe coding is killing indie hacking. Shipping fast with AI made a first version cheap. A founder replacing his own bills, on purpose, is a different scene: Pieter Levels swapping paid tools for code he generated. A storefront login is the case where a missed check is someone else’s library. oliwarner’s point still applies there. The ask, and the person who knows what to ask, change what comes back.

On 10 November, a separate Hacker News thread, “AI usage generates a fragile codebase”, stood at 638 points. That thread caught the week’s mood on Hacker News.

Is Humble Bundle safe to use right now?

Humble had published no statement, and the reports of a returning check were still coming from users.

Neowin reported that the change was not announced on Humble’s social accounts, and that neither the store nor its parent had responded. Jankified, on 11 November, described Humble as silent. PC Gamer had reached out to Humble. Kotaku had asked Humble for comment. Aftermath had reached out to Ziff Davis. On 13 November, @humble was posting bundle promotions, and had not posted about the redesign.

Reports that a check had returned were narrower than the old authenticator setup, and they were still second-hand. Aftermath noted Reddit users saying 2FA was re-enabled for them. Pirate Software, in a reply on 12 November, wrote: “They updated it this morning to have mandatory email based 2FA.” Humble had not confirmed that report. PrivacyAffairs had already described an emailed code as an alternative at sign-in, a different bar from Humble Guard plus an authenticator app. If your own settings show a second step again, the gap above is still what reporters described on 11 and 12 November.

PC Gamer’s advice to readers was to remove saved payment details. PrivacyAffairs writes that Humble replaces keys only for purchases in the last 14 days, so a purchase older than that sits outside the window that report describes. Kotaku reported that redeemed and unredeemed labels had disappeared, so the library was harder to read in the same week the login was weaker. That is the stake for a buyer, and for an indie developer whose game is in those accounts.

The reporting covers the buyer side: sign-in, password change, email change, library labels, and the help page. It does not describe a broken creator dashboard.

Earlier this month, other builders were told to rotate API keys at the company that issued them, after Trigger.dev and GitBook said an attacker may have reached stored secrets. Different incidents. The shared habit is to go and look at the control, instead of waiting on a statement that has not arrived.

What should you check before shipping an AI-built rewrite?

The useful part is a short list: the account behaviour reporters said was missing or wrong, plus the neighbouring paths a rewrite can drop quietly. Run it whether an agent wrote the code or a person did. Who wrote the Humble site is unproven. The missing account screens were reported in detail.

  1. Two-factor authentication carried over. Login still prompts, and settings still let someone add or remove it, including on accounts that already had it on. That is the gap Pirate Software, xavdid, and PC Gamer described.
  2. Changing a password asks for the current password. Kotaku reported no such check. dtech would expect a model to require the old password by default. The r/humblebundle line PC Gamer quoted asked for password changes to come down until that was fixed.
  3. Changing an email confirms to the old address. Kotaku reported verification only to the new address, and wrote “We’ve tested this too”.
  4. Session behaviour matches what you used to offer. Kotaku reported no stay-logged-in control.
  5. A saved payment method can be removed. PC Gamer told readers to remove saved payment details because the login was weaker. On a rewrite of your own, confirm that removal still works before you ship.
  6. Purchase history and the library survived, including labels the old product used. Kotaku reported that the redeemed and unredeemed distinction was gone.
  7. The help centre matches the live product. Humble’s two-step article was still published, and PC Gamer said the FAQ still encouraged 2FA, while the settings screen in those reports did not offer it.

oliwarner’s experience is the other half of the same list. In that comment, generated auth tended to arrive with a real feature set when the person knew what they were asking for. midasz’s line is that a walkthrough, including one you hand to a model, would have caught some of what did not make sense. u2secured_team asked for guard rails and a human check. sinbadbuilds asked for a pass “from a security pov” before launch.

Aftermath’s June sources said two engineers remained after the summer layoffs. A small team can ship a storefront. The public test, for an AI rewrite or any other rewrite, is whether those paths still work on the day the new site replaces the old one.

What do you think? Would you trust an AI-written sign-in you had not reviewed yourself, and what is on your list before a rewrite goes live?

FAQ

Did Humble Bundle remove 2FA?

Pirate Software posted on 11 November 2026 that Humble Bundle login no longer prompted for 2FA, and that the add-or-remove setting was gone. PC Gamer's Joshua Wolens reported the next day that people who had 2FA on could sign in with email and password, while the FAQ still encouraged it. PrivacyAffairs' Miklos Zoltan described a password, an emailed code, or Google, and called the emailed code an alternative, not a second step. He wrote that Ory, which can do 2FA, is not turned on. Pirate Software later reported mandatory email-based 2FA. Aftermath noted Reddit users saying it was re-enabled. Humble and Ziff Davis had not confirmed the return.

Was the new Humble Bundle site vibe coded?

Nothing public proves the new site was vibe-coded. Kotaku's Alicia Haddick called it what appears to be an all-new vibe-coded redesign, and a 12 November Hacker News thread (349 points, 213 comments) blamed vibecoding in the title. Riley MacLeod at Aftermath wrote that there is no proof of that. PrivacyAffairs wrote that nothing public shows it. Commenter brindleth said the article offers no direct proof the site was vibecoded, and that the accusations are vibes-based. xx__yy wrote that AI does not produce bad software, people do. trvz wrote that this is not AI's fault. oliwarner wrote that generated auth came with solid features when the ask was specific.

Is Humble Bundle safe to use right now?

At the time of writing, Humble and Ziff Davis had published no statement. Neowin reported the change was not announced on Humble's social accounts, and that the store and its parent had not responded. PC Gamer, Kotaku, and Aftermath each said they had asked for comment. PC Gamer recommended removing saved payment details. PrivacyAffairs writes that Humble replaces keys only for purchases in the last 14 days. Some users reported 2FA returning, including Pirate Software's note of mandatory email-based 2FA and Reddit comments Aftermath cited. Those reports are unconfirmed. An emailed code is a different bar from the old authenticator app.

What should you check before shipping an AI-built rewrite?

Before a rewrite ships, click the account paths, whether an agent wrote the code or a person did. Confirm two-factor authentication carried over, including for people who already had it on. Confirm a password change asks for the current password, and an email change notifies the old address. Confirm stay logged in still matches the screen, a saved payment method can be removed, and the library survived, including redeemed and unredeemed keys. Confirm the help centre matches the live product. midasz said a model walkthrough would have caught some gaps. u2secured_team asked for guard rails and human checks. oliwarner said the result tracks what you know to ask for.

Why did Ziff Davis say Humble Bundle needed a new site?

PrivacyAffairs reports that Ziff Davis told investors the relaunch was days away, and quotes CEO Vivek Shah saying the old platform interfered with conversions and customer experience. That is the company's stated reason for the new site. It does not describe how the code was written. Aftermath reported that Ziff Davis laid off Humble engineers over the summer, and that workers said in June only two engineers remained at Humble. A relaunch reason and a June headcount are both on the record. Neither one shows that an agent wrote the new site.