Creator accounts usually get taken over in one of three ways: a password reused from an old breach, a fake login page, or a "sponsorship" email carrying a file that steals your logged-in browser session.
The fix is a short list, and the order matters. Lock down your email first, because whoever controls it can reset the password on almost everything else. Then put every password in a password manager, and stop opening files from people you don't know. Those three cover most of the risk; the rest of this guide is the follow-up work for the week after.
This is the same baseline CISA, the US cybersecurity agency, pushes in its four basic steps for staying safe online: strong passwords with a password manager, multi-factor authentication, software updates, and recognising phishing. I've reordered it for people whose income sits behind a handful of logins.
Do these three today
- Turn on multi-factor authentication (MFA) for your main email account, and save the recovery codes. Use the strongest method your provider offers (see the table below). Print the recovery codes or store them somewhere that isn't the phone you use to sign in, because losing that phone is the usual way people lock themselves out.
- Install a password manager and change your email, domain registrar and payment passwords to long random ones. CISA's advice is at least 16 characters, random, and never reused. You don't have to fix all your accounts in one sitting. Do the important ones now and replace the rest as you log in to them.
- Adopt one rule: never run a file that arrives with an unexpected business offer. The next section explains why this one is on the list.
The fake brand deal: how creator accounts get taken over
Google's Threat Analysis Group documented a long-running campaign against YouTubers in its report on cookie-theft malware. The attackers found creators through the business email address listed on their channel and sent a forged collaboration offer that impersonated a real company. Once the creator agreed, they got a link to a "software download" page, by email or inside a PDF on Google Drive. Running the file sent the browser's session cookies to the attacker. Hijacked channels were then sold or rebranded to stream cryptocurrency scams.
A session cookie is what keeps you signed in after you've entered your password and your MFA code. Someone who copies it can act as you without ever logging in, so MFA doesn't get a chance to stop them. That's why a rule about files sits on the same list as MFA.
In practice:
- Treat any offer that asks you to download a game, an editing tool, a "media kit" installer or a password-protected archive as hostile until proven otherwise. A real brief is a document you can read in the browser.
- Check the sender's domain against the company's real website, and if the offer looks real, reply through a contact address you found yourself.
- If a message links to a login page, don't use the link. Open the site from your own bookmark and sign in there.
- Keep doing actual outreach on your own terms. If you pitch brands for direct deals, you'll know which conversations you started.
The FTC's guide to recognising phishing lists the other common hooks: fake "suspicious activity" alerts, invoices you don't recognise, and requests to confirm payment details. CISA adds a point worth remembering: bad spelling is no longer a reliable tell, since AI tools make phishing emails read cleanly.
Which MFA method to choose
CISA's position is that some MFA types are better than others, but any MFA is better than no MFA. Its guidance describes FIDO-based sign-in, which covers passkeys and hardware security keys, as the only widely available phishing-resistant kind, and text-message codes as a last resort.
| Method | Survives a fake login page? | Use it for |
|---|---|---|
| Passkey or hardware security key | Yes | Email, registrar, anything that offers it |
| Authenticator app code | No, a fake page can relay the code | Accounts without passkey support |
| Text message code | No, and it's also exposed to SIM swapping | Only when nothing else is offered |
A passkey is tied to the real site, so a lookalike page has nothing to capture. It can't protect a session that's already signed in, though, so you still need the no-unknown-files rule.
Don't skip MFA on an account just because SMS is the only option. Turn it on, and ask your mobile carrier what protection it offers against SIM swaps.
