Qrious Secure Profile
Qrious Secure

@qriousec

Followers
1K
Following
4
Media
11
Statuses
19

Debugger is main vehicle to satisfy our boundless Qriousity. A non-profit 🇻🇳 hackers' club driven by passion.

Joined November 2022
Don't wanna be here? Send us removal request.
@qriousec
Qrious Secure
7 days
@seadragnol, one of our juniors shared his kCTF exploit and the lesson learned: digging through unreproducible Syzkaller reports for gold.
1
14
75
@qriousec
Qrious Secure
2 months
RT @thezdi: We have a full win!! Ho Xuan Ninh (@Xuanninh1412) and Tri Dang (@trichimtrich) from Qrious Secure used a 4 bug chain to exploit….
0
9
0
@qriousec
Qrious Secure
2 months
RT @thezdi: Fantastic! Ho Xuan Ninh (@Xuanninh1412) and Tri Dang (@trichimtrich) from Qrious Secure successfully demonstrated their exploit….
0
8
0
@qriousec
Qrious Secure
3 months
Thanks to LLM, we migrated our hacking kungfu to web3 successfully!
Tweet media one
0
2
15
@qriousec
Qrious Secure
5 months
The hibernation of our Linux kernel team has ended. Our team member @SeaDragnoL has successfully pwned the COS 109 target of Google's kernelCTF!
Tweet media one
2
2
87
@qriousec
Qrious Secure
5 months
We kick off 2025 with a 0day in Mesa driver of Chrome GPU found by @kyr04i and @__suto
Tweet media one
2
8
77
@qriousec
Qrious Secure
5 months
Our V8 sandbox escape found by @__suto and @lanleft_ has been derestricted .
0
30
141
@qriousec
Qrious Secure
6 months
A brief JavascriptCore RCE story by @lanleft_ and An Nguyễn.
0
56
224
@qriousec
Qrious Secure
7 months
Santa gave us freshly new JSC 0day ✌️
Tweet media one
2
4
96
@qriousec
Qrious Secure
8 months
Tweet media one
1
1
21
@qriousec
Qrious Secure
8 months
RT @bienpnn: This is the report of the Windows LPE bug that I used in TyphoonPwn this year.
0
8
0
@qriousec
Qrious Secure
1 year
After CVE-2024-0223, we reported the bypass and it was assigned CVE-2024-3516:.Months later, someone else reported another variant and Google decided to give up and allow Chrome's GPU to crash instead of fixing the issue.
Tweet media one
1
2
17
@qriousec
Qrious Secure
1 year
hey #googlectf folks please give us a v8 sbx challenge so we can make our recent submitted 0day useful one last time
Tweet media one
1
4
52
@qriousec
Qrious Secure
1 year
CVE-2024-0517 - Chrome V8 maglev compiler optimization RCE vulnerability, has been derestricted (along with exploit code). This was reported by our teammate @__suto.
Tweet media one
1
25
92
@qriousec
Qrious Secure
1 year
RT @__suto: I successfully exploited #V8ctf using . CVE-2024-0517, writeup and exploit will be published later.
0
13
0
@qriousec
Qrious Secure
1 year
Additionally, last year our teammate @bienpnn also pwned Linux kernel on kernelCTF with a 0-day, that has been fixed and assigned CVE-2023-4244. So far, we have successfully pwned 2/3 liveCTF hosted by Google. We are going to aim for kvmCTF in the future.
Tweet media one
0
5
34
@qriousec
Qrious Secure
1 year
Our teammate @__suto has just pwned V8 JavaScript engine on Google's V8CTF version M120 using a 0-day exploit.
Tweet media one
0
3
38