<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Android on DevOps &amp; Homelab Adventures</title><link>http://lab.8devops.com/tags/android/</link><description>Recent content in Android on DevOps &amp; Homelab Adventures</description><generator>Hugo -- 0.166.0</generator><language>en-us</language><lastBuildDate>Mon, 06 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://lab.8devops.com/tags/android/index.xml" rel="self" type="application/rss+xml"/><item><title>BadBox in the Living Room: Forensic Analysis of a VSeeBox V3 Plus</title><link>http://lab.8devops.com/posts/2026-07-06-badbox-vseebok-forensics/</link><pubDate>Mon, 06 Jul 2026 00:00:00 +0000</pubDate><guid>http://lab.8devops.com/posts/2026-07-06-badbox-vseebok-forensics/</guid><description>A VSeeBox Android TV box sat quarantined on VLAN 666 for months. When I finally turned it on to investigate, the traffic capture told a story I didn&amp;#39;t expect: VSeeBox is running the malware infrastructure themselves.</description></item></channel></rss>