DEV Community

Cover image for How Hackers Weaponized DEV.to's Mention System to Spread a Phishing Scam
Jack
Jack

Posted on

How Hackers Weaponized DEV.to's Mention System to Spread a Phishing Scam

Hackers exploited automated mention emails

If you received an email today saying "Mandatory user verification" with a 12-hour deadline, DO NOT CLICK THE LINK.

the email

I woke up to an email notification from DEV.to stating that a user named ๐˜ฟ๐™š๐™ซ ๐™Ž๐™ช๐™ฅ๐™ฅ๐™ค๐™ง๐™ฉ ๐™๐™š๐™–๐™ข had mentioned me in a comment. Upon opening the post, I found a massive phishing campaign that has successfully infected the platform.

Here is a complete technical breakdown of how this scam works, why you received the email, and what you should do.

๐Ÿšฉ The Anatomy of the Attack

1. The Fake Post & Account
The scammer creates a post titled "Mandatory user verification". The author's name uses Unicode characters (๐˜ฟ๐™š๐™ซ ๐™Ž๐™ช๐™ฅ๐™ฅ๐™ค๐™ง๐™ฉ ๐™๐™š๐™–๐™ข) to bypass text filters and look like an official DEV admin. The account itself is a bot (e.g., @gfdgfsgfdsgf).

Discussion on: ๐™ˆ๐™–๐™ฃ๐™™๐™–๐™ฉ๐™ค๐™ง๐™ฎ ๐™ช๐™จ๐™š๐™ง ๐™ซ๐™š๐™ง๐™ž๐™›๐™ž๐™˜๐™–๐™ฉ๐™ž๐™ค๐™ฃ

2. Abuse of the Mention System
You didn't receive a direct email from the hacker. You received an automated notification from DEV.to because the hacker spammed @mentions of hundreds of users in the comments. The platform's legitimate email system was weaponized to deliver the threat directly to your inbox.

3. The Malicious Link
The post instructs you to log in via a third-party URL shortener: tr.ee/dev-to.
RED FLAG: DEV.to will never use a URL shortener for authentication. If you click it, you are redirected to a pixel-perfect clone of the DEV.to login page designed to steal your credentials (Phishing).

4. Psychological Triggers
The post uses classic social engineering tactics: artificial urgency ("12 hours deadline") and fear ("Failure to verify will result in restricted access") to make you act before you think.

Hello world!

5. Hiding the Evidence
The bot spams comments to bury the post. If you look at the comments, legitimate users asking "Is this real?" have their comments hidden by the post author so other users won't see the skepticism.

๐Ÿ›ก๏ธ How to Protect Yourself

  • Never use URL shorteners for Auth: If an email asks you to click a bit.ly, tr.ee, or tinyurl link to log in, it's a scam.
  • Check the URL: The official domain is dev.to. Always verify the root domain before entering your password.
  • Don't Panic: DEV.to will never threaten to delete your account within 12 hours without a prior warning.
  • Report & Block: Use the DEV.to "Report Abuse" button on the post.

๐Ÿ”ง What DEV.to Needs to Fix (For the DEV Team)

While the community stays vigilant, this incident highlights some critical infrastructure vulnerabilities:

  1. Rate Limiting on Mentions: New accounts should not be allowed to mention 100+ users in a single comment.
  2. Unicode Homograph Protection: Names using mathematical alphanumeric symbols (๐˜ฟ๐™š๐™ซ) should be flagged or normalized to prevent impersonation.
  3. Email Sanitization: Perhaps DEV.to could include an automated warning banner in mention-notification emails if the parent post is flagged by the community.

Stay safe out there, developers. Never let an API or a bot rush you into giving up your credentials.

Have you received this email too? Let me know in the comments below (if they are visible ๐Ÿ‘€).

Ping : @devteam @ben

Top comments (24)

Collapse
 
francistrdev profile image
FrancisTRแด…แด‡แด  •

Thank you Jack for announcing this.

Collapse
 
ggle_in profile image
Jack •

<3 its my pleasure Boss Francis!

Collapse
 
fm profile image
Fayaz •

Come on! You guys are DEVs. Let's join forces and spam the spammer ๐Ÿคฃ

Collapse
 
ggle_in profile image
Jack •

already check back the post are deleted ;p~ fast hand thooo; well its on 2 posts too.

Collapse
 
ggle_in profile image
Jack •

i was gonna send the cc's info, but i suddenly remember,.... i dont have cc! elqfrin doesnt help either! :p

Collapse
 
jarvisscript profile image
Chris Jarvis •

Yep got two notifications. One post was gone when I checked it. The other was up then , I flagged it. Sure many others did as well. It is gone now.

Rate Limiting on Mentions: New accounts should not be allowed to mention 100+ users in a single comment.

Nobody should be able to mention 100+ users. no need for that.

Collapse
 
gnomeman4201 profile image
GnomeMan4201 •

yeah thanks for letting people know. i didn't receive an email but a notification with a list of what im guessing is suspicious names maybe. idk but my account name is on it. i figured the notification about the scam, is the scam itself.

Collapse
 
ggle_in profile image
Jack •

Whether it's an email or an in-app notification, it's the same @mention exploit. They just tagged hundreds of people in one go. If your name is on a massive list of random usernames, it's definitely a phishing attempt. Nice work spotting the suspicious list!

Collapse
 
gnomeman4201 profile image
GnomeMan4201 •

The mass tagging is already a red flag, but impersonating DEV support is an even bigger one.

Collapse
 
nullandvoid_ profile image
Jyanthi •

A most commendable piece of work. Thank you for bringing this matter to light and elucidating how even trusted notification systems can be turned against their very users. Such awareness is invaluable in an age where vigilance is paramount. I sincerely appreciate the time and effort you have devoted to sharing these insights. Much obliged for this enlightening read!

Collapse
 
gnomeman4201 profile image
GnomeMan4201 •

Quick update: I got another one today, except this time it actually reached my email instead of just my DEV notifications.
What interests me is that weโ€™re still seeing these mass mentions after yesterdayโ€™s posts were taken down. Deleting the posts helps, but it doesnโ€™t necessarily address how theyโ€™re reaching people in the first place. Iโ€™d be curious whether DEV has any limits on how many unique users an account can mention within a certain time period, rather than just per comment. Otherwise, couldnโ€™t someone simply spread the mentions across multiple comments or accounts?

Seems like thatโ€™s the part worth looking into maybe.

Collapse
 
ggle_in profile image
Jack •

I've reaching out creating issue on GitHub to help in forem, and we have same celebral vibes in here.

Collapse
 
maame-codes profile image
Maame Afua A. P. Fordjour •

This happened to loads of people today, so posts like this really help spread the word. I just hope no one falls for it, especially newer members who might not know DEV would never ask them to log in through a random link.

Collapse
 
ggle_in profile image
Jack •

100%. The scale of this attack was insane. Newer members are prime targets because they haven't built that "spidey sense" for DEV's real emails yet. We just gotta keep reminding everyone that DEV doesn't do shady short links.

Collapse
 
fm profile image
Fayaz •

This one isn't asking for password though. This one is asking for Credit Card info.

Collapse
 
fm profile image
Fayaz •

Don't worry, I've checked it using a safe environment ๐Ÿคฃ

Collapse
 
johnnylemonny profile image
๐—๐—ผ๐—ต๐—ป •

Woke up to one of those mention notifications myself - thanks for writing this up so quickly to raise awareness.

Weaponizing the platform's legitimate notification pipeline is devious because standard email security checks (DKIM, SPF, sender domain) all pass completely clean. Seeing hundreds of tagged handles paired with an artificial 12-hour deadline and a URL shortener was an instant red flag, but newer members could easily get caught off guard. Strict rate limits on @mentions for newly created accounts and homoglyph filtering on display names definitely need to be prioritized.