not around here anymore lol. previous statements may not represent me correctly anymore

it/its | she/her
Joined November 2018
lexi <img src=x onerror=alert(1)> retweeted
Illinois Senate: Kirk (R), Giannoulias (D) Still Neck-and-Neck...
6
1
lexi <img src=x onerror=alert(1)> retweeted
Kirk Street Suspect: ESCAMBIA - He was shot in the neck while trying to protect his home now deputies say th... http://tinyurl.com/3ytggdc
lexi <img src=x onerror=alert(1)> retweeted
Replying to @cubsncards
@cubsncards @BullsBlogger LOL! I didn’t even notice Hinrich! Watch that neck, Kirk!
1
1
lexi <img src=x onerror=alert(1)> retweeted
when you ask a google engineer to fix a bug and then genuinely hit you with the “i got this job by doing 500 leetcode problems” stare
8
45
3
2,811
87,900
hi @starlabs_sg! first, congrats on the shell on issues.chromium.org/issues/5…! heartbreaking news: google likely wont pay you the fullchain bonus that you're hoping for :( we're in the same boat: pvr upstream known but unpatched bug w/ angle bypass. they dont wanna pay for that 1/2
reported a chrome fullchain (web -> shell) on pixel 10 to google. got a 9.6 cve (cve-2026-87464) and a fix in chrome. now they bend the rules and refuse to pay the fullchain bonus bc one of the vulns in the chain was an unpatched nday. total payout: $2.5k. despite cve + shell :|
3
3
53
6,346
if you wanna take a look at how my chain like that worked: issues.chromium.org/issues/5… also, as the thread says, this is not explicitly stated in the rules but they still refuse to pay out. if you wanna get in contact to try to do something about this feel free to dm though! 2/2
14
496
more likes than dollars from google #WhitehatMoment #GotPaidInExposure #WhyDoIEvenBother
reported a chrome fullchain (web -> shell) on pixel 10 to google. got a 9.6 cve (cve-2026-87464) and a fix in chrome. now they bend the rules and refuse to pay the fullchain bonus bc one of the vulns in the chain was an unpatched nday. total payout: $2.5k. despite cve + shell :|
3
4
108
2,197
reported a chrome fullchain (web -> shell) on pixel 10 to google. got a 9.6 cve (cve-2026-87464) and a fix in chrome. now they bend the rules and refuse to pay the fullchain bonus bc one of the vulns in the chain was an unpatched nday. total payout: $2.5k. despite cve + shell :|
91
165
31
3,006
272,286
update: appealed the decision and they denied it because of this "rule". "Demonstrations of exploits against an active release of a Stable or Beta build of Chrome" is what it says in the rules at bughunters.google.com/about/…. nothing about everything being new. they just made that up
3
4
346
13,104
with the same argument they could deny any submission that uses known gadgets. next up they're gonna ban calling `system()` because they were already aware that `system()` can lead to RCE? this is a ridiculous rule that is not even documented anywhere. just insulting.
5
3
384
11,182
im also friends with satoshi nakamoto btw #bitcoin
2
8
1,085
i love spreading misinformation on the internet
7
956
975d90ec5b5b2d41184f20bdac25bc134da104c003a4e94e17932982f6c30ad6 5.html 1d45d228a25c0b8bf6dd805f6341ac4ad8b1ae6f719e3c56e2564c5e048c218d notes 😃🔫
This quoted post is unavailable.
10
2,198
hey @Boltzhq i made you a canary for october that you can use as a drop-in replacement via a GPG vuln in case you dont have time to update it in october =) (jokes aside you might wanna switch away from cleartext signature verification like this as its vulnerable to gpg dot fail)
1
8
1,061
in concrete terms, you want a raw canary.txt and a separate canary.txt.sig signature file that users should verify with `gpg --verify canary.txt canary.txt.sig` and an attacker can't trivially edit your "signed" text anymore
5
645