Vibe coding security risks: what to check before launch
Vibe coding security risks can quietly drop two-factor login and account checks in a rebuild. Learn what to test before you launch.
On this page
Vibe coding security risks are easy to miss because a rebuilt app can look finished while quietly dropping protections that users relied on. A recent case shows how this plays out. Humble Bundle redesigned its website and store, and critics say the new version lost features, including two-factor authentication. This article uses that case to explain what to check before you launch an AI-built app or store, and how to test a redesign so nothing important disappears.
What happened with the Humble Bundle redesign
In November 2026, GamingOnLinux reported that Humble Bundle had remade its website and store, and that many customers were unhappy with the result. The GamingOnLinux article describes complaints across social media and in reader inboxes, with some people accusing the company of launching a store that was not ready and was built in a rushed, "vibe-coded" way.
These are accusations as the article reports them, not confirmed facts about how Humble Bundle built the site. The specific complaints were:
- Two-factor authentication appeared to be removed. The article calls this a major security concern.
- Email changes did not seem to check the old address. According to the report, this could make it easier for someone to take over an account.
- The account and library view lost basic tools. Readers said it was harder to browse past purchases, and filtering between redeemed and unredeemed keys was gone.
- Bundle payment allocation was harder to find. The option to adjust where money goes was reportedly tucked at the bottom of the page behind an expand control.
The reviewer also pointed out that the older design was not fancy but mostly worked, and that the new one seemed to offer little beyond removed features. Whether every complaint is accurate is an open question. The useful lesson is that a redesign can remove things users depend on, and the people affected often find out after launch.
Why vibe-coded redesigns break things users depend on
Vibe coding means describing what you want to an AI tool and accepting the code it produces, often with limited line-by-line review. This approach can get a working app in front of people quickly. It also makes it easy to lose behavior that nobody wrote down.

When you rebuild an existing product, the old version holds many implicit requirements. A filter that people use every week, a confirmation step on an email change, or a second login factor may never have been listed as a requirement. If the new version is generated from a fresh description, those behaviors can disappear without anyone deciding to remove them.
Security settings are especially vulnerable. Two-factor login and email change verification sit in the background. They do not look broken when they are missing, and the people who would notice are often the ones at risk. A user who loses a second factor usually learns about it only when someone else gets into their account. That is why security checks need to be part of the launch process, not something you assume the new version inherited.
Is a vibe coded app safe to launch?
A vibe coded app can be safe to launch, but the tool that built it does not decide that. Safety comes from testing. If you cannot say how the app handles login, password resets, account changes and payments, you have not finished checking it, regardless of how polished it looks.
If you want a broader view of the review process, the FromScratch guide on how to review AI-built code covers the general approach. The checks below focus on the areas where a redesign is most likely to cause real harm.
Vibe coding security risks to check before launch
Use these checks on every version that handles accounts, personal data or money. Run them on the new version, then run them again after every significant change.

Authentication checks
Start with the front door. Confirm that:
- Login works with a normal account and with an account that has two-factor authentication turned on.
- Two-factor authentication still asks for the second factor, and that setting can be enabled and disabled as intended.
- Password reset sends a working link and expires as expected.
- Failed logins are handled sensibly and do not reveal whether an account exists.
If your old version had two-factor authentication, the new one must have it too, or you need a documented decision to remove it.
Account change checks
Changing an email address or password is a common route for account takeover. Confirm that:
- Changing an email sends a verification message to the new address.
- The change also notifies or requires confirmation from the old address, so the current owner can stop an unwanted change.
- Changing a password asks for the current password or a verified session.
- Users receive a notice when these settings change.
The Humble Bundle complaints centered on this exact gap, which is why it belongs on every checklist.
Data access and payment checks
Next, check what each user can see. Log in as two different test accounts and confirm that each one sees only its own purchases, orders, records and files. Try to open another user's item by changing an address in the browser, a common way data leaks.
For payments, test the full flow with test cards. Confirm that charges, refunds and any split or allocation settings behave as they did before. If a setting that controls where money goes is moved or hidden, treat that as a change to review, not a cosmetic update.
A feature inventory to stop regressions
The most reliable defense against lost features is a written list. Build the list before you change anything, because it captures what the old version actually does, not what you remember.
How to test a redesign before launch
Follow these steps:
- List every feature in the current version. Include small items such as filters, sorting, search, export buttons and settings. Walk through each page and note what it does.
- Mark each item as kept, changed or removed. Any item marked removed or changed needs a written reason and a named person who approved the decision.
- Test the list on the new version with real accounts. Do not stop at the happy path. Try the edge cases: an empty library, a deleted item, a user with many records, a user on a slow connection.
- Record the date each item was last tested. This shows what has been checked and what has not.
- Keep the list alive. The next change should start from it, not from memory.
What to check when a redesign removes features
Removed features are the most common source of complaints, so treat each removal as a risk. Ask:
- Who uses this feature, and how often?
- Is there another way to do the same task?
- Is the replacement as easy to find and use?
- Does removing it affect security, billing or legal obligations?
If you cannot answer these questions, do not remove the feature yet.
Build it with FromScratch
You can build a feature audit app to track these checks, so the list lives in one place your team can update. Here is the process with FromScratch, the AI app builder:
- Open the FromScratch chat and describe the app. You can say what it should do in plain language. You do not need to write code.
- Ask for the core pieces in the same message. Include the fields you need: feature name, status, sign-off and last-tested date.
- Refine it by chatting. Ask for changes such as adding a search bar, a filter by status, or a login screen. Each request updates the app.
- Use the live preview to test it. Check that the status options, sign-off field and checklist behave as you expect before you publish.
- Use versions to protect your work. Every change is saved, so if a later edit breaks something, you can restore an earlier version.
- Publish when it passes your checks. You can publish to a public URL or to your own custom domain.
- Get a second opinion for sensitive apps. If your app handles accounts or payments, have an expert review it before you ship.
To start, paste this prompt into the FromScratch chat:
Build a feature audit app where I can list every feature of my current app with a status of kept, changed or removed, plus a sign-off field and a last-tested date. Include a checklist of must-keep behaviors such as login with two-factor authentication, email change confirmation sent to the old address, and filters for redeemed and unredeemed items. Add a simple login so only my team can edit the list.
If you are new to this kind of build, how to build an app with AI step by step walks through the basic workflow. For context on the approach itself, what vibe coding is explains the basics in plain English.
FAQ
Is vibe-coded software always insecure?
No. Vibe-coded software is not automatically insecure, but it needs explicit checks for authentication, data access and account changes. Do not assume a generated app inherited the protections of the old version. Test those areas directly before launch.
Can I rebuild my app without losing features?
Yes, if you inventory the features first and test each one on the new version. Write down every page, filter, setting and security control, then mark each as kept, changed or removed. Any removal should have a reason and an approver.
What should I do if I find a regression after launch?
Restore the previous version while you fix and retest the change. Keeping saved versions makes this safer, because you do not have to rebuild from memory. Then add the missing behavior to your feature list so it is tested in future releases.
Do I need to know how to code to check security?
No, but you do need a clear checklist and a habit of testing. You can check whether two-factor login works, whether an email change sends confirmation to the old address, and whether users see only their own data. For anything involving accounts or payments, ask an expert to review the app before you publish.