Member Avatar for happygeek

You've got to love this one. A Bangladesh government website, for the Rapid Action Battalion, was hacked last week. It was one of those hacktivism style affairs, with the home page defaced and a message left in its place.

The message, in this instance, read:

"GOVERNMENT DOES NOT TAKE ANY STEP FOR ICT DEVELOPMENT. BUT PASSED A LAW ABOUT ANTI-CYBER CRIME. YOU DO NOT KNOW WHAT IS THE CYBER SECURITY OR HOW TO PROTECT OWNSELF. LISTEN. HACKERS R NOT CRIMINAL. THEY R 10 TIME BETTER THAN YOUR EXPERT. WE ARE GINIOUS THAN YOU CAN'T THINK. DEFACED FROM BANGLADESH."

Trouble is, this particular 'ginious' started the defaced page announcement with a bloody big banner saying "HACKED BY SHAHEE_MIRZA" which is not exactly brilliant thinking in terms of hiding your identity. Especially when that is your real name.

Nor, for that matter, is adding your real email address at the bottom of the page...

According to "Within 24 hours, the authorities had arrested 21-year-old computer science student Shahee Mirza, and three of his friends in connection with the hacking. According to RAB, Mirza has confessed to hacking the website and the sites of at least 22 other organizations. Mirza claims that he had no malicious intentions in defacing the websites."

  • 4 Contributors
  • 3 Replies
  • 558 Views
  • 5 Days Discussion Span
  • Latest Post Latest Post by Thinka

Dani AI

Generated

Good laugh — and a useful lesson. As observed, public defacements that include any kind of brag or signature are textbook operational‑security failures; ’s reminder about the jurisdiction bit is also important because who you call and how the case is handled depends on where the target and attacker are. ’s reaction is understandable; ’s “lol” too—this sort of thing looks dumb because it is.

If you run a website and ever see a defacement, treat it as an incident, not just a cosmetic problem. Immediate steps (preserve evidence first):

  1. Take offline screenshots and save copies of the modified files.
  2. Preserve server logs and make a full disk image before any changes.
  3. Isolate the affected host from the network to stop lateral movement.
  4. Check access logs, FTP/SFTP/SSH history, scheduled jobs and web-upload folders for webshells or backdoors.
  5. Rotate credentials, revoke exposed keys, and inform your host/ISP.
  6. Rebuild from known‑good images after you’re confident you’ve removed persistence; don’t blindly restore a compromised backup.

Longer‑term hardening that actually helps prevent repeat incidents: keep OS, web server and CMS/plugins patched; remove unused services; enforce least privilege on web directories; use SFTP/SSH (not plain FTP); enable multi‑factor authentication for admin accounts; deploy file‑integrity monitoring and a web application firewall; and run periodic vulnerability scans and disaster‑recovery drills.

Final note: it’s tempting to treat this as a joke, but defacements often signal deeper access. For defenders it’s a wake‑up call to close gaps. For anyone thinking “cool trick” — remember that traceable bragging is self‑incrimination and has real legal consequences.

Recommended Answers

All 3 Replies

Member Avatar for hbipul

The blogger is dumb as well, coz its not in India, its Bangladesh Govt website, its a different country.

Member Avatar for scru

Are you kidding me?

Member Avatar for Thinka

Lol... good to know that somethings in this world aren't getting better...

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.