feature request: allow setting breakpoints without having obfuscator debugger statement loops get in the way
I actually wrote a separate blog post about this! Changing the debugger keyword :)
see: https://nullpt.rs/evading-anti-debugging-techniques
Show HN: I'm building a browser for reverse engineers
21–30 of 58 posts
Re: Show HN: I'm building a browser for reverse engineers
#22This is such an eye opening, and really interesting. It reminded me of projects like XprivacyLua that "expose" the different calls and request from android apps. Great work!
Re: Show HN: I'm building a browser for reverse engineers
#23Neat investigation but I didn’t totally follow how the project would be useful for reverse engineering, it seems like a project that would mostly be useful for evading bot checks like web scraping or AI automation.
Re: Show HN: I'm building a browser for reverse engineers
#24...and power users. This is a browser that acts in the interests of the user, something that the mainstream authoritarian technocracy is actively trying to destroy and has been ever since they removed "View Source" from its customary place.
Re: Show HN: I'm building a browser for reverse engineers
#25Earlier quoted context omitted.
Yeah, there's a pretty overwhelming amount of browser APIs and functionality which isn't always (well-)documented to learn about. If I recall correctly Proxies wouldn't be detectable (seems to be supported by https://exploringjs.com/es6/ch_proxies.html#sec_detect-proxi... ) so long as your injected content script runs first (otherwise other code could presumably override the Proxy constructor). You should also be abl…
To note, there are undocumented detections to even Proxys, for example using `in` operator in v8 (such as `proxiedFunc in 1` for some proxied function). Really cool to see a project like this.
How do you use `in` in v8 to detect proxies? I assume its a difference in the exception, but the message and the cause were the same in both direct and proxied `x in 1`.
Re: Show HN: I'm building a browser for reverse engineers
#26"toString theory" is an incredible title for that section
Re: Show HN: I'm building a browser for reverse engineers
#27You can just use Proxy to get around toString shenanigans and prevent any detection whatsoever.
no you cannot since you can throw an exception and your proxy will be leaked leading to a detection.
Re: Show HN: I'm building a browser for reverse engineers
#28For anyone that doesn't want to maintain a fork of chromium, just download the PDB and hook it at runtime for spoofing and/or dumping call logs. For hook itself just add your dll as a dependency in the PE structure.
Re: Show HN: I'm building a browser for reverse engineers
#29[flagged]
Re: Show HN: I'm building a browser for reverse engineers
#30Not to comment on the rest of article or the author's goals, but it's absolutely possible to use a content script (dynamically injected into the `main` world, as opposed to the default `isolated`, for example: https://github.com/tbrockman/browser-extension-for-opentelem... ) and Proxy's ( https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe... ) to hook (most? if not all) Javascript being executed in the webp…
I have a project (in my rather long project backlog) that involves hooking JS APIs to download youtube videos. I'm worried that if my extension (or a similar extension) gained enough popularity, youtube would start inspecting the relevant JS objects to see if they'd been replaced with proxy instances. Aside from playing a hooking/patching game of cat and mouse, I don't think this is fully solvable without modifying t…
Was just about to comment this I’ve played that exact cat and mouse game before there’s also another fun way to hook I used to like by doing something like Object.defineProperty on Object.prototype to globally hook onto something and you can do lots of stuff with that it’s pretty useful in user scripts