Nov 18, 2026 · 9 min read
13,000 Fake YouTube Copyright Notices Sent via LearnWorlds
Between November 7 and 14, one attacker turned about 570 free trials on the LearnWorlds course platform into a phishing relay: the welcome email became a copyright complaint, and LearnWorlds' own mail system delivered it to YouTube creators. The link led to a fake YouTube claims portal and then to a real Google sign in page.
Most phishing gives itself away in the sender line. This campaign did not, because the sender was real. LearnWorlds, a Cyprus based platform for selling online courses, confirmed to The Register that an attacker used its trial accounts to send around 13,000 fake copyright notices to YouTube creators in a single week. Security researcher Marcus Hutchins, of WannaCry fame, was one of the recipients, and his write up on X walked through the whole trap.
Key Takeaways
- LearnWorlds CEO Panos Siozos says the attacker created around 570 free trial accounts between November 7 and 14, 2026, and sent around 13,000 phishing emails through the platform's welcome email feature.
- 9,853 of those emails came from trial accounts between November 7 and 9, and 3,723 came from one paid account on November 14, according to Siozos.
- The emails linked through a real youtube.com redirect to a fake YouTube copyright portal, which sent victims to an official Google sign in page that Hutchins says hands attackers the Google account and its YouTube channel.
- LearnWorlds says it found no evidence of unauthorized access to customer schools or personal data, and that it cannot count clicks because the attacker disguised the link.
- YouTube's copyright strike help page says real copyright strikes show up in YouTube Studio under Active copyright strikes, and official notices come from no-reply@youtube.com.
How Did an Attacker Send Phishing From LearnWorlds?
According to LearnWorlds, the attacker never broke in; they used a feature as designed, at scale. LearnWorlds lets a course owner add students to a school, and adding a student triggers a welcome email. Siozos told The Register: "In each trial they added their own list of target addresses and rewrote the standard welcome email as a fake copyright notice. Adding those users triggered the welcome email from our sending address."
The timeline, as LearnWorlds gives it:
- November 7: the first email goes out, from trials opened with automated tools that got past the platform's limit on trials per customer.
- November 9: LearnWorlds blocks the first sender. A second wave starts within 40 minutes.
- November 10: all trial accounts are removed, after 9,853 emails.
- November 14: one paid account sends 3,723 more before LearnWorlds removes it.
Hutchins' first post said LearnWorlds "may have been hacked." The company's position is that nothing was breached: in its telling, no credentials were stolen, and a sign up flow and an email template did what they were built to do. The company says it has tightened bot checks and now holds new accounts whose emails trip fraud flags.
That pattern is familiar. Our report on phishing sent through legitimate platforms covered DocuSign and QuickBooks lures built the same way, and the Brevo incident showed what happens when the sending platform itself is compromised. LearnWorlds sits between the two: no breach, but the platform's own sending address did the delivering.
What Did the Fake Copyright Emails Look Like?
The emails were vague legal threats with a deadline and one link. Screenshots that Hutchins posted to X, and others shared, show two versions, both from noreply@t.us1.learnworlds.com:
- Hutchins' copy: display name "Ann Hernandez LearnWorlds," subject "Important Copyright Notification: LearnWorlds Content Usage Review." It told the reader to see "the supporting documentation submitted by LearnWorlds."
- An earlier copy, dated November 9: display name "Learworlds," subject "Formal Demand Regarding Copyright Infringement — Response Required Within 72 Hours," signed by "The Learworlds Legal & Compliance Team." The recipient who posted it pointed out the brand name is misspelled three times.
Both links started with https://www.youtube.com/redirect?q=, so the visible domain was YouTube's own. The real destination sat in the q= value: copyright-policy[.]com in Hutchins' email and youtubestudiocopyright[.]help in the other. Hutchins listed what felt off: the email "cited no specific copyright violations, didn't reference my channel by name or link to any videos, was sent on a Saturday morning, and YouTube has a built-in copyright system to handle exactly this." November 14, the day of the paid account wave, was a Saturday.
How Did the Google Sign In Trap Work?
The fake portal personalized the threat, then handed the victim to a genuine Google page. Per Hutchins' screenshots, copyright-policy[.]com showed a YouTube branded "Copyright Claim Review" page asking for a channel handle. It then displayed his real channel, with 145,000 subscribers and 102 videos, asked "Is this your channel?", and opened a "DMCA Claim Portal" that named "Moodle Pty Ltd" as the rights holder, which contradicts the email's own claim that LearnWorlds had filed the complaint. That mismatch alone is a red flag. The next step opened a Google sign in pop up at accounts.google.com.
Hutchins wrote that signing in there "will give the hackers control over the Google account they sign in with, enabling them to steal both the Google account and associated YouTube channel." Neither he nor LearnWorlds has published the app name or the permissions the page requested. The Register notes the description aligns with OAuth consent phishing, where a real Google login is followed by a permission screen and, if the victim accepts, the attacker's app receives access tokens to the account.
This is not a one off kit. In April 2026, Malwarebytes described a fake copyright strike campaign at dmca-notification[.]info that also pulled each creator's real profile picture and subscriber count into the scare page. Our coverage of fake YouTube sponsorship emails shows the other favorite lure for creators.
Why Did Email Authentication Not Stop It?
Email authentication proves which domain sent a message, not whether the message is honest. Sender authentication exists to catch forged senders. Here nothing was forged: LearnWorlds' own system sent each email from its own address. The DMARC standard, RFC 7489, says so directly: "DMARC does not produce or encourage elevated delivery privilege of authenticated email," and it "does not attempt to solve all problems with spoofed or otherwise fraudulent email."
We checked LearnWorlds' DNS on November 18, 2026. The main domain, learnworlds.com, publishes a strict DMARC policy (p=reject). The sending subdomain, t.us1.learnworlds.com, has its own record set to p=none, with an SPF record that authorizes Mailgun. That relaxed setting is not what let the phishing through, though. We have not seen the message headers, but a message LearnWorlds really sent would have been expected to authenticate under either policy. Google's sender guidelines require SPF or DKIM from every sender and DMARC from bulk senders; a legitimate SaaS platform meets those rules by design.
Filters still caught some. Hutchins' screenshot shows the message in his Gmail inbox, tagged External. The November 9 copy shows up in another mail client's junk folder. Same sender, opposite verdicts, which is what you would expect when the only signal left is the content.
Why Email Users Should Care
Any SaaS product that lets a stranger type a message and pick the recipients is a potential phishing relay: course platforms, form builders, invoicing tools, event invites. Free trials make the cost of a fresh sending identity close to zero. LearnWorlds claims more than 14,000 business customers, per The Register, and the platform is white label, which is why Hutchins warned that "you may not realize you're a user of their platform." A learnworlds.com address in your inbox looks routine to many people.
For creators, the stakes sit behind one login. The same Google account holds the inbox and the channel, so a single approved sign in can cost both. Treat a passing authentication check as a statement about the pipe, not the person typing into it.
How Can Creators Spot a Fake Copyright Strike?
Check YouTube Studio, not the email. YouTube's copyright strike help page says real strikes are emailed, but that "Official notifications come from no-reply@youtube.com," and that you can see them by signing in to YouTube Studio and looking on the Dashboard "under Active copyright strikes." Its creator safety page adds: "YouTube will never ask for your password, email address, or other account information."
- Ignore the sender, open Studio yourself. Type studio.youtube.com into the address bar. No active strike there means no strike. Even a no-reply@youtube.com sender is not proof: in 2023, phishers abused YouTube's share by email feature to send from that exact address.
- Read the redirect. A youtube.com/redirect link is only as safe as its q= value. Hover and read the end of the URL.
- Distrust third party claims portals. YouTube handles strikes inside Studio, so a separate website asking you to "verify" your channel is a warning sign.
- Turn on a passkey. YouTube's safety page recommends 2-Step Verification with a passkey as the second method for the strongest protection against phishing. A passkey protects your password, not your judgment: The Register notes that in consent phishing victims sign in and pass MFA on genuine pages, so the permission screen that follows is the part you must refuse.
What Should You Do If You Signed In?
Change your password and cut off any app you do not recognize. LearnWorlds' advice, via The Register: "Anyone who signed in on the fake page should change their Google password and review their account's recent security activity." Then follow Google's linked apps help page:
- Go to myaccount.google.com/linkedapps.
- Select Access to your Google Account, then the app you want to review, and choose See details.
- For anything you did not knowingly approve in the past week, select Remove access, then Confirm.
Security teams can hunt for the t.us1.learnworlds.com sender and for youtube.com/redirect links whose q= value points at copyright-policy[.]com or youtubestudiocopyright[.]help. The "72 Hours" subject line is a further indicator.
What We Could Not Verify
We did not receive one of the emails, so we have not seen its authentication headers. Nobody has published the OAuth app name or the scopes it requested, and LearnWorlds says it cannot count clicks. We did not find a public statement from LearnWorlds; its figures come from its CEO's comments to The Register. The email details come from screenshots that Hutchins and another recipient posted on X.