salchoman Profile Banner
Sal ꙮ Profile
Sal ꙮ

@salchoman

Followers
648
Following
6K
Statuses
952

Software Entomology & Archeology at Google. Previously BurpSuite Crawler & Scanner team. Personal friend of Carlos Montoya. 🧀

Djibouti
Joined April 2012
Don't wanna be here? Send us removal request.
@salchoman
Sal ꙮ
10 years
The answer to life the universe and everything..!! http://t.co/Aj2pgzra2j
Tweet media one
0
4
11
@salchoman
Sal ꙮ
13 days
RT @chessMan786: 8 Bytes, many meanings
Tweet media one
0
184
0
@salchoman
Sal ꙮ
15 days
if() I get a CSS injection...
@intenttoship
Intent To Ship
15 days
Blink: Intent to Prototype: CSS if() function
1
0
1
@salchoman
Sal ꙮ
3 months
@WeizmanGal @MtnBer @we1x @ddworken @arturjanc Haha, it's been on my TODO list for a while. I can't make any promises on delivery but I can promise to bump it up! Finding these is tricky, I used a custom build of Fuzzilli with some success, but there's much more to be found out there. Don't nerd snipe me, y'all!
1
0
5
@salchoman
Sal ꙮ
3 months
@MtnBer @WeizmanGal @we1x @ddworken @arturjanc Nice! There's a whole world of them that we found back when we did this work. It's an area of PP that is still under researched IMHO with lots of potential, see my other reply!
0
0
0
@salchoman
Sal ꙮ
3 months
@MtnBer @WeizmanGal @we1x @ddworken @arturjanc Btw, this is also how you can find PP gadgets in native JS funcs. We have a list of them that still needs publishing :/ [1] is an awesome example of stealing an array's values by polluting ` - mostly useful for sandbox bypasses tbf
1
0
4
@salchoman
Sal ꙮ
3 months
@WeizmanGal @we1x @MtnBer @ddworken @arturjanc You can't make a shim out of this proposal because the `prototype` property is still there, which is why it needs to be done at the language level. At Google, we delete the `__proto__` property and freeze top level prototypes, which isn't as nice as what the proposal achieves :)
1
0
3
@salchoman
Sal ꙮ
4 months
RT @SecurityMB: Check out the video in which I’m talking with @kkotowicz about Google VRPs. Learn how you can start hacking Google! Let me…
0
9
0
@salchoman
Sal ꙮ
4 months
Love to see the constant stream of posts over the past couple months where malware developers are struggling to 1/ lift cookies and 2/ use them effectively thanks to and other changes from our Chrome/Identity colleagues 👏
@RussianPanda9xx
RussianPanda 🐼 🇺🇦
4 months
I heard stealers are struggling to restore Google🍪👀 Translated post (#LummaC2): Guys, since Google has tightened the screws 🔩 and while we are exploring automation options, here are some temporary tips for working with Google accounts ☀️ Tips ⚡️ 1. For logging in, you now need to select an almost perfect location, with accuracy down to the area/region/state level 🇺🇸. 2. Each Google account now requires its own profile in an anti-detect browser. If before you could use one profile for multiple accounts, that’s no longer the case due to Google’s restrictions ☹️. 3. If you are using account recovery methods that work under the hood with multilogin, you must recover the key 🔑 using a proxy that matches the location, with accuracy down to the area/region/state level 🇺🇸. 4. If you are logging in via cookies obtained from step 3, the proxy used for login must match the proxy used for recovery 🚨. Why are these more than just tips? 🙄 1. Open your browser on your computer, log into your account. Then turn on the VPN, clear the browser cookies, and try to log into Gmail. If previously it would let you log in after such actions, now it won’t. This confirms that there’s a trigger on the IP address causing the logout 🕊️. 2. Log into your Google account, then export the cookies (you can do this using any cookie management extension), open a second browser, and import the cookies there. It will log in. Now import any other Google profile into that same browser, even your own, and you’ll get logged out 😒. 3. The third tip is confirmed by the first point in this paragraph. 4. This can easily be verified by the same IP trigger but with 100% accuracy. The login IP for cookies must match the IP used for recovery 🧐. It’s possible that Google may ease these restrictions soon, as based on our calculations, these tightened measures are also affecting regular users 🥺.
Tweet media one
1
0
4
@salchoman
Sal ꙮ
4 months
A different kind of programming competition in 1983
@BBCArchive
BBC Archive
4 months
#OnThisDay 1983: Micro Live visited Datarama - the Radio West show that was broadcasting computer software programs over the airwaves. Talk about a wireless download...
0
0
0
@salchoman
Sal ꙮ
4 months
RT @kryc_uk: A new era for security in #MicrosoftEdge and it's web integrations as #MicrosoftBing now supports nonce-based CSP on Edge Desk…
0
3
0
@salchoman
Sal ꙮ
5 months
Write-up* and ...used in... 🤦🏻‍♂️
0
0
1
@salchoman
Sal ꙮ
5 months
RT @_MG_: The exploding Hezbollah pagers situation is an incredibly impressive supply chain attack by Israel (most likely). I am sure more…
0
670
0
@salchoman
Sal ꙮ
5 months
RT @aszx87410: there is a challenge in idekCTF 2024 called srcdoc-memos made by icesfont, it's about iframe, sandbox, CSP, navigation, sess…
0
45
0
@salchoman
Sal ꙮ
7 months
Check out the most thorough end to end explanation of Google's recipe to eradicate entire classes of web bugs at scale
@we1x
Lukas Weichselbaum
7 months
My @LocoMocoSec keynote slides on "Google's Recipe for Scaling (Web) Security" are online now:
Tweet media one
0
2
11
@salchoman
Sal ꙮ
7 months
Go get yourself some nice prototype pollution bugs to submit to the Google VRP and tag me when you publish your 'thank you javascript' post :)
@GoogleVRP
Google VRP (Google Bug Hunters)
7 months
🚨💰 Google VRP Reward Update 💰🚨 Good news, we are significantly increasing the reward amounts offered by the Google VRP! Look out for up to 5x higher payouts and a maximum reward of $151,515! Details here:
0
1
20
@salchoman
Sal ꙮ
8 months
@bsdaemon Cool talk! Was there ever a write up or CVE on the `!0` bug you mentioned?
1
0
2
@salchoman
Sal ꙮ
11 months
RT @maxpl0it: @_manfp’s Firefox renderer bug is a beauty that takes advantage of an optimisation implemented just 3 months ago. Let’s break…
0
97
0
@salchoman
Sal ꙮ
11 months
Yet another prototype pollution in Firefox!
@thezdi
Trend Zero Day Initiative
3 years
Confirmed! Manfred Paul (@_manfp) demonstrated 2 bugs (prototype pollution and improper input validation) in Mozilla Firefox and has earned $100K and 10 Master of Pwn points! #Pwn2Own #P2O15
Tweet media one
0
1
8