I recently came across a suspicious post on DEV.to that was pretending to be from the DEV Support Team.
The post was titled “Mandatory user verification” and claimed that users had to verify their accounts within 12 hours or their accounts would be restricted.
It directed users to this shortened URL:
tr.ee/dev-to
After opening the link, I was shown a fake verification page claiming that my account was temporarily restricted and that I needed to verify my identity.
The suspicious part? It appeared to request bank card information for account verification.
I don’t believe a normal DEV.to account verification should require your bank card details.
🚩 Red flags I noticed
- The post impersonated the DEV.to support team.
- It used a shortened external URL instead of the official DEV.to domain.
- It created urgency with a 12-hour deadline.
- The email and post even mentioned different deadlines.
- The verification page appeared to request financial information.
🛡️ How to stay safe
- Never enter bank or card details on suspicious verification pages.
- Check the domain before entering any personal information.
- Don’t trust an account just because its display name says “Support Team”.
- Access DEV.to directly through https://dev.to.
- Report suspicious posts and accounts to the DEV.to team.
I only opened the link and did not enter any information.
I’ve also reported the post through DEV.to’s abuse reporting form.
Images:
—
Please stay alert and share this warning with other developers.
A little awareness can prevent someone from losing access to their account or exposing their personal information.



Top comments (4)
The actual DEV.to support team should take action fast as possible as they can
Good call reporting it and posting the screenshots. A 12-hour deadline plus a card form is about as clear as these get.
For anyone who gets the same notification: you can see where a short link goes without opening it.
curl -sI https://tr.ee/dev-toprints theLocationheader when the shortener does a normal redirect, so you get the landing domain without rendering the page. Some phishing kits redirect with JavaScript or show a harmless page to non-browser clients, so a clean result isn't proof.Once you have the landing domain, its age usually gives it away. Pages like this tend to sit on domains registered a few days before the campaign. If you'd rather not read raw WHOIS, Ask WhoisFreaks (ask.whoisfreaks.com) answers "is this domain safe?" in plain English from WHOIS, DNS and threat-feed data. Disclosure: I work on it. Your first search doesn't need an account.
I liked your idea
Is the project started recently?
Thanks! Yes, Ask is new, we launched it very recently. It sits on top of the WHOIS, DNS and threat data we already run at WhoisFreaks, and the chat part is what's new.
If you try it on the tr.ee link's landing domain, I'd like to hear whether the answer was useful or missed anything. Early feedback like that is what we're after right now.