<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>pentest on Florence Njeri</title><link>https://florence-njeri.github.io/njeri/tags/pentest/</link><description>Recent content in pentest on Florence Njeri</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 03 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://florence-njeri.github.io/njeri/tags/pentest/index.xml" rel="self" type="application/rss+xml"/><item><title>Android Pentesting with AndroGoat</title><link>https://florence-njeri.github.io/njeri/posts/androgoat/</link><pubDate>Tue, 03 Feb 2026 00:00:00 +0000</pubDate><guid>https://florence-njeri.github.io/njeri/posts/androgoat/</guid><description>Android Pentesting # To sharpen my skills, I recently took a deep dive into AndroGoat—a deliberately insecure Android application designed to showcase the most common OWASP Mobile Top 10 vulnerabilities.
In this post, I’ll walk through how I combined both static and dynamic analysis to uncover hardcoded secrets, bypass security checks with Frida, and extract sensitive data from local storage.
My pentesting toolkit:
My pentesting tookit included:
Jadx-GUI: For decompiling and reading Java/Kotlin source code.
The Android Debug Bridge (adb)**: The &amp;ldquo;command line&amp;rdquo; for interacting with the emulator on android studio.
Frida: For dynamic instrumentation. Instrumentation is the art of imjecting new functionality to the application at runtime e.</description></item></channel></rss>