<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mobile Exploits on Florence Njeri</title><link>https://florence-njeri.github.io/njeri/tags/mobile-exploits/</link><description>Recent content in Mobile Exploits on Florence Njeri</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 01 Mar 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://florence-njeri.github.io/njeri/tags/mobile-exploits/index.xml" rel="self" type="application/rss+xml"/><item><title>8ksec - AndroPseudoProtect: Ultimate Device Security</title><link>https://florence-njeri.github.io/njeri/posts/andropseudoprotect/</link><pubDate>Sun, 01 Mar 2026 09:00:00 +0000</pubDate><guid>https://florence-njeri.github.io/njeri/posts/andropseudoprotect/</guid><description>8ksec - AndroPseudoProtect: Ultimate Device Security # Exploiting Exported Components and Bypassing Security By Obscurity Mechanisms # The goal of this exercise was to develop an android application that exploits Android&amp;rsquo;s IPC by disabling AndroPseudoProtect.apk&amp;rsquo;s security functionality.
My initial thought process was that this would likely involve exploiting improperly exposed components. Specifically, if sensitive components are configured with exported=true, an attacker application could potentially access internal functionality via Inter-Process Communication (IPC), manipulate behavior, and bypass security controls. This assumption proved to be correct.
Installing and Running the App # Upon launching the app, the application asks for access to all files.</description></item></channel></rss>