2025 Microsoft MVR-2024 Q1/2/3/4/MVR | 2023 H1-4420. Vulnerability researcher @msftsecresponse,@Hacker0x01 and @intigriti,I like pwning,together we hit harder

Joined May 2022
Over the past several days, we have been listening to the conversation around coordinated disclosure and the relationship between security researchers and vendors. We recognize that this relationship is both critical and, at times, fragile. We deeply value the security community, and will continue to take your feedback seriously. To be clear about our approach to legal matters, we have no intention to pursue action against individuals conducting or publishing their security research. When an individual breaks the law and engages in malicious activity causing real harm to our customers, we will work with law enforcement as appropriate. We recognize the work that goes into researching and submitting a vulnerability. We are committed to approaching every interaction with transparency, clear communication, and professionalism. We continue to believe strongly in Coordinated Vulnerability Disclosure as the foundation for protecting customers and improving our products. Each year we process a high volume of vulnerability reports. That volume continues to grow and will continue with the rise of AI-enabled research. We acknowledge that some interactions have fallen short and are working to learn from them. Many of us have experience on both sides of this work, as researchers reporting vulnerabilities and as responders triaging and assessing them. That perspective informs how we approach this feedback and the importance we place on getting it right, particularly as the volume and complexity of research continues to grow. The security community plays a vital role in helping us protect customers. We are committed to maintaining a constructive and respectful relationship and growing together. We know that, given the nature of this work, there will at times be misunderstandings. We remain committed to engaging in good faith and to providing a respectful and professional experience for all researchers, regardless of past interactions.
Readers added context they thought people might want to know
The root of this statement is a post by a security researcher that stated MS revoked the access to their reporting account. When the researcher asked for explanation, his account got deleted. He got no answer. This escalated further by MS deleting the github account as well. deadeclipse666.blogspot.com/2026/05/dear-m…
294
103
162
470
599,516
[POC2025] SPEAKER UPDATE 👥 Bocheng Xiang(@crispr_x) & HeeChan Kim(@heegong123) - "Follow the Link: Building Full-Chain Local Privilege Escalation on Windows" #POC2025
5
1
48
10,307
I'm very happy to receive this gift from MSRC @msftsecresponse. Although vulnerability research can be challenging, if you stay passionate, work hard, and persevere, your efforts will always be rewarded. Good luck to all!
1
10
786
Grateful for his trust, inspired by his legacy — forever remembered. 🌹🕊️
Peace out world. Best wishes to all. ALS has won this battle, but hopefully not the war!
5
595
Simon retweeted
Good Morning! Just published a blog post diving into Windows Kernel LFH exploitation in the latest Windows 24h2 build, Focusing on controlled allocations to achieve arbitrary read/write in the kernel. r0keb.github.io/posts/Modern…
4
79
1
309
20,389
Proud to be ranked 42nd on the MSRC 2025 Most Valuable Security Researchers list! Thank you so much @msftsecresponse
The Microsoft Researcher Recognition Program offers public thanks and recognition to security researchers who help protect our customers by discovering and sharing security vulnerabilities under Coordinated Vulnerability Disclosure. Today, we are excited to recognize this year’s 100 Most Valuable Researchers (MVRs), based on the total number of points earned for each valid report. Please join us in celebrating this year’s MVRs, including our top 10: 1. 🥇 VictorV (@vv474172261) 2. 🥈 wkai 3. 🥉 Suresh Chelladurai 4. Anonymous 5. Adnan (@adnanthekhan) 6. Dhiral Patel (@dhiralpatel94) 7. Nan Wang (@eternalsakura13) and Ziling Chen 8. Anonymous 9. @0x140ce 10. Azure Yang (@4zure9) See the full list of this year’s 100 MVRs, in addition to our Azure, Office, Windows, and Dynamics 365 leaderboards: msft.it/6011s6KxU #bugbounty
15
1,004
Two of my previously reported vulnerabilities were fixed in Microsoft's July Patch Tuesday. And left a mark on the MSRC Q2 leaderboard. Thank you! @msftsecresponse
Replying to @msftsecresponse
Shoutout to the other incredible researchers who made this quarter’s leaderboard. Your work and partnership is deeply appreciated! @scwuaptx @niraj1mahajan @4zure9 @eternalsakura1 @Xtytia0922 @scianto05 @0xSombra @shhnjk @c0d3nh4ck @sim0nsecurity @hexnomad @AnupamAS01 @guilhermesgi
1
13
1,094
cool to be tagged and truly honored
3
415
CVE-2024-43639: Remote Code Execution in Microsoft Windows KDC Proxy. The Trend Research Team dives deep into this bug to look at the root cause and complexities of exploitation. They also provide detection guidance. Read the details at zerodayinitiative.com/blog/2…
4
51
152
13,954
This is my first time pwning Microsoft Edge. msrc.microsoft.com/update-gu…
1
1
22
2,372
I have made MSRC’s 2024 Q4 leaderboard! #BugBounty #msftsecresponse
1
7
1,178
Thank you for the amazing swag @msftsecresponse! what a fantastic way to kick off the New Year 2025. Wishing you friends all the best for the year ahead! #bugbounty #Microsoft #MSFT #microsoftrewards
1
9
978
Six months ago, I reported a vulnerability in Office to Microsoft that had been existing for a decade, it's been fixed now, as per the reference below msrc.microsoft.com/update-gu… #bugbounty #msrc
11
757
To help protect against NTLM relay attacks, we’ve enabled Extended Protection for Authentication (EPA) by default in Windows Server 2025. This update strengthens key services like Exchange Server, Active Directory Certificate Services (AD CS), and LDAP, making identity compromise and unauthorized access more difficult. Learn more about these security improvements and how they can help protect your systems in our blog post: msrc.microsoft.com/blog/2024…
5
43
124
19,122
Severity will be based on the part addressed by this vendor rather than the impact of the vulnerability #hackerone #BugBounty
4
525
I got two CVEs related to Local privilege escalation from Ivanti forums.ivanti.com/s/article/…
1
7
1,154
I have made MSRC’s 2024 Q3 leaderboard #msrc #BugBounty #msftsecresponse
1
13
1,946
PoC and wirte-up for CVE-2024-38200: Microsoft Office NTLMv2 Disclosure Vulnerability github.com/passtheticket/CVE… Patch: msrc.microsoft.com/update-gu…
2
48
1
169
13,206