Imamul Mursalin (@vulnbot0) header
Imamul Mursalin (@vulnbot0) profile picture

Security enthusiast aka Cyber Security Researcher

Dhaka, Bangladesh
Joined March 2020
Photo by Imamul Mursalin (@vulnbot0)Photo by Imamul Mursalin (@vulnbot0)Photo by Imamul Mursalin (@vulnbot0)Photo by Imamul Mursalin (@vulnbot0)Photo by Imamul Mursalin (@vulnbot0)Photo by Imamul Mursalin (@vulnbot0)Photo by Imamul Mursalin (@vulnbot0)Photo by Imamul Mursalin (@vulnbot0)Photo by Imamul Mursalin (@vulnbot0)Photo by Imamul Mursalin (@vulnbot0)
Alhamdulillah , I become father of a boy . Pray for my son & wife
10
110
10,049
@3ncryptSaan spare some for me 🙏
1
1
613
Bad luck 🥲
1
43
1,868
Really appreciate this types of teams .
17
682
From a normal Rxss to account takeover to rce in any instance , It can be a cve Alhamdulillah #Account_takeover ,#RCE , #Rxss
1
1
47
2,109
Imamul Mursalin retweeted
We are working non-stop to resolve this issue. Binance will cover all losses. As a precaution, all deposits and withdrawals are temporarily suspended while our team conducts security checks, freezes funds, and works with law enforcement. We are working around the clock and will share a full post-mortem once the investigation is complete. Please rely only on official Binance channels for updates. This is an industry-wide effort, and we are grateful to partners across the ecosystem who have moved quickly to help freeze affected assets. We will continue to share verified updates through official Binance channels. User funds are safe.
778
1,197
434
6,975
1,116,061
Just pwned another ssrf on @Bugcrowd
1
43
2,258
one of my finest finding till now , zero interaction, direct authorisation code theft leads full account takeover
40
1,549
SSRF on Kibana Connector , duplicate. No worries will find more🥲
2
2
33
1,087
account takeover on android app via hardcoded DevTool backdoor
5
2
80
7,854
Let’s hope for the best #bugcrowd
2
51
2,324
First bug on web3 #immunefi
2
69
3,119
Hi @Hacker0x01 what is this? As a hunter how I can know the internal policy? This issue was reported on july 2026, And currently on resolved state . And I was able to bypass that fix. Hackerone triager zeus closed it by saying internal policy. It’s seems like joke .
4
81
8,260
5 dups in a raw 🥲
6
74
2,390
DOM XSS via Unsanitized Filter Input in ECC Queue Logs
2
3
76
2,886
It’s totally disappointing @gitlab agent auto closed my recent submission by just matching the submission title . The original report currently on resolved state then how I got duplicate of that submission? Please @gitlab have a look on this .
1
1
62
4,395
not bad 😪
17
1,168
Companies should value security researchers who find and responsibly disclose these issues instead of dismissing the impact after fixing them.
I reported an OAuth flaw back in February that could lead to account takeover of users’ connected accounts. After the issue was fixed, the response was essentially “there’s no impact” because the believe the flaw is on the OAuth provider side.
1
3
442