Dev.to Security 🔐 Cybersecurity 👁 0 📖 1 min read

⚠️ DEV.to Users: Watch Out for Fake Account Verification Emails and Posts!

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 hou

⚠️ DEV.to Users: Watch Out for Fake Account Verification Emails and Posts!

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

  1. Never enter bank or card details on suspicious verification pages.
  2. Check the domain before entering any personal information.
  3. Don’t trust an account just because its display name says “Support Team”.
  4. Access DEV.to directly through https://dev.to.
  5. 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:

The notification
—

Their profile

—

The post

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.

📰 Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.