<?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>Git-Forensics on ThreatProphet</title><link>https://threatprophet.com/tags/git-forensics/</link><description>Recent content in Git-Forensics on ThreatProphet</description><generator>Hugo -- 0.163.0</generator><language>en-us</language><lastBuildDate>Tue, 09 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://threatprophet.com/tags/git-forensics/index.xml" rel="self" type="application/rss+xml"/><item><title>From Gamifly to AjunaVerse and AlchemyMVP: Parallel Weaponization of a Shared Poker Repository Lineage</title><link>https://threatprophet.com/posts/2026-06-09-ajunaverse-alchemymvp/</link><pubDate>Tue, 09 Jun 2026 00:00:00 +0000</pubDate><guid>https://threatprophet.com/posts/2026-06-09-ajunaverse-alchemymvp/</guid><description>Forensic comparison of two parallel GitHub repositories derived from the Gamifly/BetPoker poker-game lineage. AjunaVerse and AlchemyMVP contain nearly identical current trees, synchronized malicious commits, redundant VS Code and npm execution paths, a cross-platform Vercel staging chain, and an env.npl registrar implant linked to the recurring TCP/1224 /api/checkStatus toolkit.</description></item></channel></rss>