twimco.Let’s talk ↗︎
Menu
Field notes / Product & engineering

Humble Bundle dropped two-factor login, then restored email codes. Before yours, list the protections nobody wrote down

Nobody ever put "ask for the old password" on a roadmap. It was just something the old site did. Humble Bundle's new site stopped doing it this week, along with a few other quiet jobs, and the people who noticed were its customers.

Editorial engraving of a tester ticking a paper list while a developer compares an old and a new laptop side by side in a bright loft.

When Humble Bundle launched a redesigned site on November 12, 2026, Kotaku and PC Gamer reported that it had no two-factor login, let a signed-in user set a new password without the old one, and sent no email-change verification to the old address. Tweakers and Radar Digital later reported that email verification codes were required at login, but authenticator apps and security keys were still unavailable. The lesson for any rebuild: write down every protection and behavior the old site did silently, then test each one on the new site with a real account before launch.

What happened

On November 12, Humble Bundle, the storefront known for pay-what-you-want game bundles, launched a redesigned website. Within hours, Kotaku and PC Gamer were reporting what it no longer did.

According to both outlets, there was no longer any way to add or manage two-factor authentication. Customers who had set it up on the old site could now sign in with just an email address and a password, never asked for a code. Kotaku also reported that a signed-in user could enter a new password without knowing the current one, and that when it tested changing an email address, no verification went to the old address. Customers also complained that the site wouldn't keep them signed in, and some reported errors when buying. PC Gamer noted that the site's own FAQ pages still encouraged people to use two-factor login, which was no longer possible.

The picture moved quickly. The Verge, also writing on November 12, said its reporter was prompted for an email access code, though not for the authenticator-app code he had previously set up. Tweakers reported on November 13 that Humble was now asking for an email verification code at login, as a default users couldn't turn off, but that authenticator apps and security keys still didn't work. Radar Digital confirmed that on November 14: email codes were back, the older app-based method was not, and there was still no word on when it would return. IGN Entertainment, Humble's owner, and its parent company, Ziff Davis, had not replied to The Verge's request for comment. The later reports did not say the password-change or email-change problems had been fixed, so treat those as of the November 12 coverage unless you've checked the current site. Kotaku and PC Gamer both suggested removing saved payment details in the meantime.

It was never a feature

Read that list again. None of it is a feature in the way a new product page is a feature. Nobody sat in a meeting and said, "This quarter we're launching asking for the current password." It was behavior. The old site did it, so nobody had to think about it.

That's why this kind of thing slips through a rebuild. A redesign starts from the screens: what should the login page look like? Everything the old login page did out of sight, such as rate limits, the check on a password change, the email to the old address and the code after the password, isn't on a screen. It lives in code and settings that nobody opens, until a new team writes a new login and builds exactly what the mockup showed.

The old site's best behavior is often the one nobody wrote down. The same thing can happen on any platform move: a saved address stops syncing, or an order email stops going to a second contact. It's rarely careless. It's that the old system was doing a job the team never knew it had.

Decision guide

What the old site did, and what the new one has to prove

ConsiderationThe old site did this quietlyThe new site must prove it
Two-factor loginAsked for a code after the passwordA test account with 2FA on is stopped at the code, every time
Password changeWanted the current password firstA signed-in tester can't set a new one without it
Email changeTold the old addressThe old inbox gets a message before anything changes
Saved cardCould be removed from the account pageA tester can find and remove it
Staying signed inRemembered you on your own deviceBehavior matches the old one, or the change is announced
Illustrative framework built around the problems reported on November 12, 2026; not a statement about Humble's systems.
The old site's best behavior is often the one nobody wrote down.

Write the list before you start

The fix is dull, and it works. Before a redesign or a platform move, spend a few days writing down every duty of the old site, from three places.

The old code. Ask the developer who knows it to walk through the login, account and checkout flows and say out loud everything that happens. Each "oh, and it also…" is a line on the list.

The help pages. Everything your FAQ and support pages promise is a duty. If a page says "turn on two-factor authentication in your security settings," the new site has to have that setting. Humble's own FAQ was still making that promise after the setting was gone.

The support inbox. Skim six months of tickets and look for the things customers rely on: "I got an email when someone changed my address," "it remembered me on my phone." Each is a behavior somebody noticed because it helped.

For each item, write one sentence about what it protects. "Stops someone with a borrowed laptop from taking over the account." "Lets a customer notice a hijacked email within minutes." If you can't say what an item protects, ask before removing it. If you can, give it an owner.

Test with a real account

A list is not proof. For each item, run it on the new site with an ordinary customer account, not an admin account and not a developer's test login. Turn two-factor login on first, then try to sign in without the code. Try to change a password with the current one left blank. Change an email address and watch the old inbox. Find the saved card and try to remove it. Close the browser and come back. If you've followed our note on what to check the morning after a replatform, this is the security version of it.

Keep a short record of what you tried and what happened, with the date and the browser. If something goes wrong a month after launch, that record tells you whether it was ever working. Two things make this go faster. Run the tests before launch with a second person watching, and make a failing test block the launch. A missing protection isn't a bug for next sprint. If it were, the week it's missing is the week somebody finds out.

Also search your own help pages for words like "two-factor," "verify," "confirm" and "security settings," and make sure each sentence is still true on the new site. It takes ten minutes and would have caught the FAQ that Humble's customers could see contradicting the product.

How the work moves

Run it in this order before launch

  1. Write the list from three places

    The old code, the help pages and the support inbox.

  2. Give each item an owner

    One named person who signs it off.

  3. Test with a real account

    A normal customer account, with 2FA turned on, not an admin.

  4. Read the help pages again

    Anything the FAQ promises has to still be true.

  5. Hold the launch if one fails

    A missing protection is a stop, not a ticket for next sprint.

Illustrative pre-launch routine; adjust to your own product.

Who should do this

If you're rebuilding an account area, checkout or customer portal, put one person in charge of what the old system did, separate from the person in charge of what the new one looks like. They'll disagree about scope, and that disagreement is the point. One of them wants to ship and the other wants to know what might break. You need both voices in the room before launch, not after. Put the sign-off in writing, with the person's name next to each protection on the list, so that on launch morning you're reading names and not guessing.

If you work with an agency, ask for the list in writing before design starts and again before launch. If they've never made one, that tells you something too. Our note on what to do when a deep link lands a signed-in customer on the login page is another example of a behavior that vanishes in a rebuild because no screen shows it.

For a team building or rebuilding a product where customers sign in, this is where we'd start in our web application work: write the duty list first, test it with real accounts and don't ship until it passes. Talk to us.

Related work: Sutton|Place

twimco.

We build alongside the people doing the work.
Bring us the problem you’re thinking about.

Related work

Sutton Place ↗︎