
Ranked as the #1 security researcher for Google Play Security Rewards Program. The founder of @OversecuredInc Android and iOS vulnerability scanners
Joined December 2015
- Tweets159
- Following188
- Followers7.3K
- Likes187
On September 24, I’m hosting a free webinar with a special guest from Vimeo where we will discuss how AI is changing attacks on mobile apps, what new risks it creates, and what security teams should prepare for.
Register here: my.demio.com/ref/uUIDncr8WxN…
I'm opening a limited 5-week free pilot for Oversecured 2.0
You’ll be able to test the new platform on your own apps
We’ll select a small group of companies for the first pilot: hub.oversecured.com/poc
I'm dreaming to talk with a strong, hands-on expert in web app security. Have interesting topics to discuss
Google form: docs.google.com/forms/d/e/1F…
On July 28, I'll host a live webinar introducing Oversecured 2.0
I'll show a new agentic approach to discover vulnerabilities, how we build vulnerability chains and create a map of attack vectors on your apps
Link to register: my.demio.com/ref/OpYJi2G3QFs…
The largest vulnerability disclosure in the mobile history!
140 vulnerabiltiies in Samsung preinstalled apps
github.com/oversecured/Samsu…
I’m looking to talk to people who work with mobile app security inside companies.
I want to better understand your real workflow, tools, pain points, and what still feels too manual.
There’s a reward of your choice for the interview.
Form: hub.oversecured.com/cusdev
[1/3] It's common to get a ParcelFileDescriptor pointing to a directory through an Android ContentProvider. But can you actually turn that into a directory listing?
[2/3] Examples:
- FileProvider pointing to files/cache directories
- A misconfigured ContentProvider that can be tricked into returning a ParcelFileDescriptor pointing to a directory
We launched Android DAST. And the first problem we hit is that login flows block everything.
So we used LLM to log in automatically. This is what debugging looks like
An attack on Android content providers that researchers might overlook
[1/4] Android has a mechanism to restrict access using the exported attribute or by requiring permissions
[2/4] But system apps ("android.uid.system" and maybe systemui) automatically bypass these restrictions and can access arbitrary components
[3/4] It's trivial to force a system app to call ContentResolver.query() or openInputStream() for an arbitrary Uri
We’re hiring a Mobile App Security Expert!
What you'll do:
- Research Android/iOS internals and ship new SAST/DAST checks
- Turn real-world findings into PoCs and write-ups
- Be the technical voice with customers: explain findings, advise architecture, guide CI/CD setup
Interested? Fill out the form: docs.google.com/forms/d/e/1F…
New Android host validation bypass technique!
[1/4] All parsed URIs in Android are android.net.Uri.StringUri objects. However, the scheme parser only looks for the ":" delimiter
[3/4] This will only work if the scheme isn't validated either. This attack can increase the impact in cases when, e.g., the victim's access token is appended to the request headers







