<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Android Security on Florence Njeri</title><link>https://florence-njeri.github.io/njeri/tags/android-security/</link><description>Recent content in Android Security on Florence Njeri</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Wed, 15 Apr 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://florence-njeri.github.io/njeri/tags/android-security/index.xml" rel="self" type="application/rss+xml"/><item><title>Insecure Storage in Android</title><link>https://florence-njeri.github.io/njeri/posts/android_storage/</link><pubDate>Wed, 15 Apr 2026 09:00:00 +0000</pubDate><guid>https://florence-njeri.github.io/njeri/posts/android_storage/</guid><description>Insecure Storage in Android # Insecure storage is still one of the easiest ways to recover sensitive data from an Android app during a pentest. Even when an app has strong network protections, it may still expose tokens, cached responses, credentials, or personal data locally. This post is a quick guide to the main Android storage locations and what they mean from a security testing perspective.
Shared Preferences # A key-value XML file that stores user preferences such as dark mode or light mode. They are also often used to store access tokens or other kinds of secrets. In itself, that is not an issue, but it makes shared preferences a very interesting target for stealing or overwriting internal files.</description></item></channel></rss>