November 19, 2026
“Never Deleted”: Tracing a Rapper Through an FBI Case File, a Defaced Page and a Public Sandbox…
Handle pivoting, public-record research, reverse image search and safe investigation practice

By Chiranjeevi C
4 min read
Spoiler warning:_ this write-up contains the full solution to a challenge on ctf.osint.industries. Try it yourself first._
TL;DR
Starting from nothing but a username, Mrb3hz4d, I tied the handle to a real person through U.S. government materials, found a defacement post he published, traced it to his social media presence, and used it to identify a rapper in a post dated August 22, 2019. The twist: the Instagram account was only reachable by changing the approach twice, once with a handle search instead of a name search and once with a public sandbox report.
- Platform: ctf.osint.industries
- Challenge: Never Deleted
- Objective: find the full name of the rapper in the clip posted on August 22, 2019.
- Starting material: the username Mrb3hz4d
- Skills: username OSINT, public-record research, reverse image search, web archive analysis, safe-browsing practice
- Tools: Google, justice.gov, web archive search, ANY.RUN reports, reverse image search
The Challenge
Investigators were building an intelligence profile on a known hacker. One of the few clues was his username. The suspect was a fan of rap music, and on August 22, 2019, he posted a short rap clip. The task: find where he published it and give the rapper's full name.
The rules were strict: passive OSINT only, no interaction with people, places, or accounts, and no authentication or recovery attempts. The flag format was OSINT{Full_Name_Of_The_Rapper}.
Step 1: Searching the handle
A search for Mrb3hz4d returned results across many pages, so the first job was triage. Rather than opening everything, I focused on official, authoritative sources, specifically material released by the FBI. Handles are easy to impersonate; government documents are much better at attributing an alias to a person. The top three results were the FBI, Wikipedia, and a U.S. Department of Justice release, all describing the same person.
Step 2: Attributing the handle to a person
The FBI material gave the real name behind the alias, Behzad Mohammadzadeh, and confirmed that Mrb3hz4d belonged to him. That turned an anonymous username into an investigable identity.
Following the next link, to justice.gov, led to a court filing that reproduced a defacement page he had published, referencing Soleimani.
Takeaway: attribute before you pivot. A confirmed link between an alias and a person keeps the rest of the investigation grounded.
Step 3: Reverse image search on the defacement
I ran a reverse image search on the defacement image. Many results came back, and one was a website flagged as not secure. I opened it and found links to his Telegram and Instagram accounts. The Instagram link redirected elsewhere when I clicked it, so I backed out immediately.
Security note: I should have opened that site in an isolated environment from the start. Insecure pages and unexpected redirects are classic malvertising and phishing vectors. In real investigations, use a sandbox, a disposable VM, or at least a hardened browser profile.
Step 4: Hitting a wall, then changing the approach
I turned to a web archive search, but searching the person's full name returned nothing. The fix was to go back to the one identifier I trusted: the original handle. Searching for Mrb3hz4d produced a result, and it was his Instagram link.
Takeaway: an alias and a real name are different search keys. If one yields nothing, try the other.
Step 5: Viewing the account safely
Searching Google for the Instagram URL surfaced a public ANY.RUN report, a malware-analysis sandbox, in which the page instagram[.]com/Mrb3hz4d had been loaded and recorded in January 2020. Opening that report showed the profile as the sandbox had captured it, so I never visited the live page or logged in. That fits the challenge's rules and its title: once a public service has captured a page, it is rarely gone for good.
Step 6: Finding the August 22, 2019 post
Going through the profile, I found the post from August 22, 2019 featuring a short clip of a rapper.
Step 7: Identifying the rapper
A final reverse image search on the rapper in the post identified him, giving the flag:
OSINT{Mohammadreza_Shayea}
The whole solution at a glance
Lessons learned
- Start with authoritative sources. Government releases beat random search hits for attribution.
- Pivot on the identifier that works. The handle succeeded where the real name failed.
- Archives preserve what people think is gone. The challenge title says it all.
- Treat investigation targets as hostile territory. Sandbox unfamiliar or insecure sites.
- Persistence pays. Two dead ends were resolved by changing the method rather than repeating the same one.
Skills demonstrated
- Username and alias research
- Using public government records for attribution
- Reverse image search and visual verification
- Web archive and public sandbox report investigation
- Operational security and safe browsing
- Adapting methodology after failed attempts
A note on ethics
This investigation used only publicly available information, in a CTF environment, about a person already named in public U.S. government documents. The same techniques can be misused. Apply them within the law, within platform rules, and with respect for privacy.
If you enjoy challenges like this, try ctf.osint.industries yourself. Feedback and alternative approaches are welcome in the comments.