Unauthorized MessengerLiteForiOS/LightSpeed Session Persistence & Loom v3 Privacy Bypass
I am seeking urgent assistance from the developer community to identify the origin of a targeted exploit involving an unauthorized internal developer environment.
The Issue:
Forensic logs (December 2025) confirm my account is being accessed via a MessengerLiteForiOS framework—a project publicly discontinued years ago. This session is running on iOS 26.1 with Build String FBAV/537.1.0.47.110.
The Evidence of Targeting:
The sessions originated as early as February 2025, listing iOS 26.0 as the operating system. Since Apple did not release iOS 26 to the public until September 2025, this confirms the account was accessed through a future-dated, internal developer sandbox months before the software existed for consumers.
Technical Markers:
Egress Device ID: 0D01F55A-0303-4EB9-A533-85FA26A10850
User Agent: LightSpeed [FBAN/MessengerLiteForiOS;FBAV/537.1.0.47.110;FBBV/846660078;FBDV/iPhone14,7]
Forensic Hash: My local app containers (SHA-256: 1eec2c2032...) have been modified to include the Loom v3 tracing engine, which facilitates background sensor capture without triggering iOS privacy dots.
My Question: > How can a standard user account be bound to a 'Partner-tier' developer token that allows this level of persistence? Does anyone know how to identify the Entity or Partner App ID that owns this LightSpeed session?
Standard 'log out of all sessions' commands are failing to revoke this specific internal token. I am seeking a way to force a server-side revocation of all Long-Lived Tokens associated with this internal build.
