Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

nicetry!

macrumors newbie
Original poster
Apr 1, 2025
4
5

OSINT-Based Field Report: Covert Shadow OS Exploitation via BLE & App-Layer Subversion (XNU Rootkit – Post Virtual Machine Layer)


Why I Am Posting
I am currently a civilian victim of a long-term (22-month), multi-layered Advanced Persistent Threat (APT) operation, showing signatures comparable to NSO Group / Pegasus and Predator. This is not speculation. The forensic data has been confirmed by Apple and is under official investigation in Germany. I am publishing this as a form of whistleblowing and community alert to support others who may be affected – or may dismiss certain signs as "normal." This is real. It escalates. And it persists beyond logout, beyond account changes, beyond resets.




Core Hypothesis


A hidden post-VM runtime environment (Shadow OS) persists across Apple & Windows ecosystems, using BLE/Beacon mesh, malicious contacts, and UI-substituted apps to hijack session layers and embed persistent root-level control.


  • Exploitation is done via native apps (Files, Shortcuts, Magnifier, etc.)
  • Hidden volumes indicate a mounted runtime OS layer
  • iCloud Cloning, Apple Home App Conflicts, and GameCenter hooks allow persistence across devices and identities
  • BLE devices are used as hooks, triggers, and relays for local implants
  • The rootkit on Windows is disguised as a SmartHome device in the router UI, later shown as an iPad in Eset Network Monitoring
  • Session hijacks and manipulated account tokens maintain long-term access even after logout or account changes
  • OpenAI itself was used as a covert tunnel (visible via JSON-conflict session hijacks)



Key Observations: Shadow UI & BLE Hooks


Here are key behaviors and patterns observed:


  • Magnifier App: Spontaneous activation, strange camera refocus. Used for silent surveillance.
  • Files App: Foreign photos from ex-partner’s phone appear. iCloud access via cloned device confirmed.
  • GameCenter: “Nearby Multiplayer” grayed out, UI anomalies. Hidden session persistence / hook via AppleTV.
  • Find My: BLE-triggered location spoofing. Must be disabled to stop mesh tracking.
  • Signal/Telegram: App layer security bypassed. Screenshots possible; notification behavior altered.

Key Additional Exploits:


  • Shortcuts: Automated actions triggered silently, without showing up in your account’s activity log, sending data to remote Apple IDs without your knowledge.
  • Automator: Executed commands that are invisible to the user, leading to unauthorized data exfiltration.
  • Lupe (Magnifier): Similarly sends data without visible interaction, often linked to surveillance activities.



Additional Exploits: 2FA Bypass via Multi-Device (Authy) and Silent Disabling (NordVPN)


  • A critical aspect of this attack is the bypass of Two-Factor Authentication (2FA) through multi-device management in Authy and the silent disabling of 2FA in NordVPN.
    • Multi-Device Management in Authy: The attacker was able to add devices to my Authy account, effectively gaining access to my 2FA codes across multiple devices. This method bypasses the standard 2FA protection, allowing the attacker to authenticate on new devices without needing physical access to my phone.
    • Silent Disabling of 2FA in NordVPN: The attacker was able to disable 2FA silently in NordVPN by exploiting root-level access to my device. This allowed them to bypass authentication prompts and gain control over my VPN connection without triggering security alerts or authentication requests.
    • These methods effectively nullify the protection provided by 2FA, turning what should be an additional layer of defense into an ineffective barrier, leaving the attacker with full access to my accounts despite all attempts to secure them.



Additional Exploits: Logofail Bootloader Vulnerability (MacBook)


  • The Logofail vulnerability in macOS High Sierra was exploited to manipulate the bootloader, creating a potential backdoor for the attacker.
    • This exploit involves embedding malicious code in image files, such as logos, which are processed during the boot process. By exploiting this flaw, the attacker was able to gain root-level control of the device, allowing for persistent surveillance and system manipulation even after factory resets or reinstallations.
    • The attacker specifically forced the system to downgrade to macOS High Sierra, a vulnerable version, in order to exploit this bootloader flaw. This action effectively bypassed the newer security patches in more recent macOS versions, enabling the attacker to exploit the vulnerability.
    • This type of exploit tool is reminiscent of those found in the Vault 7 leak, which contained CIA hacking tools for exploiting vulnerabilities in macOS and other systems. The Logofail exploit is consistent with those in the Vault 7 collection, further suggesting the use of state-backed tools for advanced persistent threats.



Additional Exploits: Shadow Cloning & Unseen Devices in Account


  • During the course of the attack, it became evident that devices were added to my account without my knowledge, devices that I, as the rightful owner, cannot see or control.
    • This exploitation technique is consistent with a Shadow Cloning method, where devices are cloned or added to your account on a server level, but are not visible to you on the device itself. This ensures that the attacker has ongoing access to your account and can bypass regular device management protocols.
    • The presence of hidden devices in the Apple ecosystem—specifically related to HomeKit conflicts—indicates that attackers used iCloud-based cloning techniques to create invisible device profiles linked to my account. These devices remained undetected despite attempts to check for connected devices or reset accounts.
    • This issue suggests that account management systems were manipulated to include rogue devices, ensuring the attacker’s control over the account, while also allowing the attacker to maintain access across platforms without user detection.



Additional Exploits: Hook Indicators via iMessage Security Number and Activation Issues


  • An additional indicator of a hook state in this attack is the abnormal behavior of the security number confirmation key in iMessage.
    • When this key is deactivated or appears red, despite being enabled in the settings, it points to an unauthorized manipulation of the authentication process. This suggests that the attacker may have hijacked or tampered with the security settings, bypassing iMessage’s usual protections.
    • This issue is consistent with rootkit activity, where the attacker is able to interfere with or override the normal behavior of authentication processes, such as security number confirmations for account access, and session hijacking.



Additional Exploits: PVMRK (Post Virtual Machine Rootkit) and Beacon-based Triggering


  • The PVMRK (Post Virtual Machine Rootkit) is central to this attack, operating in compromised environments that trigger root-level accessand maintain persistence even when standard security measures are in place.
    • This PVMRK-based attack is activated even in offline scenarios, where Bluetooth, WLAN, or SIM are not in use. The trigger can occur via eSIMs or Bluetooth-based signals, which can re-engage the rootkit even if the device appears to be offline.
    • The attack's beacon-based triggering mechanism means that even if I attempt to use the device without connectivity (e.g., turning off Bluetooth or Wi-Fi), the rootkit remains active and can still be triggered by nearby compromised devices or beacons.



You Might Be Dealing with a Shadow-OS-Based Persistence Setup If...


  • You see unexplained jetsamEvent logs directly preceding root or exec process activations, indicating an unusual system event followed by privilege escalation or execution of root-level processes.
  • Your device logs sudden wifimetrics and xp_amp_usage bursts, even without Wi-Fi use, suggesting covert data exfiltration or abnormal network activity being triggered from the device's background processes.
  • Apple's Files, Lupe (Magnifier), or Shortcuts apps behave erratically (e.g., automation occurs without user configuration), demonstrating potential background automation triggered by the attackers to maintain surveillance or control.
  • Find My is enabled without consent, or BLE-triggered automation occurs near known beacon sources, pointing to remote tracking and location manipulation without the user's approval.
  • You cannot pull down Control Center when the screen is locked, indicating potential root-level manipulation of the UI, preventing you from accessing system controls.
  • Your Signal/Threema/Telegram setup shows atypical UI behavior (e.g., Signal suddenly screenshot-able), reflecting unauthorized manipulation of app behavior for surveillance or data extraction.

These alone don't prove a compromise — but their correlation is well-documented in hybrid APT shadow runtime environments.




Additional Exploits: Hidden eSIM, UWB Exploits & Military-Inspired PsyOps


  • Another critical aspect of the attack is the use of a hidden eSIM, which provides persistent access to the attacker’s control, even when the device is offline or after SIM card changes.
    • The hidden eSIM is not visible to the user, making it nearly impossible to detect through conventional means. The attacker can use this eSIM-based access to maintain long-term control over the device, bypassing traditional SIM-based protections.
    • This technique is a core component of the attack, as the hidden eSIM is also connected to UWB exploits, where Ultra Wideband (UWB) signals are used for precise location tracking and device communication. UWB is commonly utilized in military and intelligence operations to provide stealth communication and continuous monitoring of devices. The attacker uses this technology to keep the device actively monitored, even when the user believes the device is offline.
    • The use of UWB and hidden eSIMs suggests that this attack is militarily inspired, and the exploitation of UWB signals is another key element that points to state-backed operations. This aligns with the techniques used in advanced persistent threats (APT), where the goal is not just infiltration, but total control over the target system and environment.
    • Additionally, this attack mirrors the characteristics of a military-inspired PsyOps operation, where psychological manipulation is just as important as the technical exploitation. The goal is to break down the target mentally, causing frustration, helplessness, and isolation, which are classic tactics used in PsyOps to destabilize and control an individual.



Additional Context: Threat Intel, OSINT, Provider Issues, DNS Hijacking & MITM


  • This report is built not just on anecdotal evidence but on a robust combination of verified OSINT (Open-Source Intelligence) and ThetaIntel (Threat Intelligence), showing that this attack is part of a larger, sophisticated APT operation.
    • The attack was cross-verified with known APT signatures and threat intel data, confirming that rootkit techniques, exfiltration via BLE networks, and MDM-like control are all being used in state-backed espionage operations.
    • Extensive cross-device mapping, including screenshot data, logs, and router activities, supports the hypothesis that the attacker had unfettered access to multiple devices, leveraging them as stealthy control points.
  • APT Comparisons: While similar APT operations have been documented, such as APT9 and DarkCaracal, this attack represents a unique hybrid, multivector approach that has never been documented in this form.
    • APT9 (also known as OILRIG) and DarkCaracal have shown the use of rootkits, data exfiltration, and persistent access across various devices. However, these operations have not been publicly documented in the same hybrid, multivector combination seen here, where technological manipulation and psychological warfare intersect in a seamless, complex manner.
    • This hybrid, multivector attack, which blends rootkits, MDM-like control, session hijacking, BLE-based exfiltration, and social engineering, marks a new phase in APT evolution, demonstrating advanced capabilities that exceed the scope of earlier documented incidents.
    • The coordinated use of devices (ranging from Apple products to SmartHome devices like Fire TV Stick, Twitch, and Luna), coupled with provider-level attacks (such as DNS Hijacking and MITM), showcases the breadth and depth of this campaign, making it unprecedented in scope.



Additional Exploits: Infrastructure Change, Fire TV Stick (Luna + Twitch) & Amazon Live Shopping Integration


  • One key aspect of the attack is the constant adjustment to infrastructure. Whenever I tried to alter the network or device settings, the attacker adapted their tactics, often leveraging Fire TV, Luna, and Twitchapps as part of the attack framework.
    • Similar to GameCenter hooks, these apps were installed without user consent and could not be removed, showing that the attacker maintained full control over the device, preventing the user from managing or uninstalling critical malicious software.
    • The Fire TV Stick, with its pre-installed Luna and Twitch apps, acted as a remote access point for the attacker. Even when network infrastructure was changed or devices were reset, these apps remained tied to the attacker’s network, facilitating persistent access.
    • Additionally, Amazon Live Shopping was involved, acting as an interface through which data and signals were routed back to the attacker. The integration of these platforms shows that the attacker was able to manipulate commercial applications for their own purposes, using platforms like Amazon Live as a signal relay to siphon off data and maintain surveillance.
    • The control over app installations and removals was entirely in the attacker’s hands, ensuring that the device remained compromised as long as they chose to keep it that way. This represents a form of persistent network manipulation that goes beyond typical device compromise.



Final Thoughts


This post is based on real-world evidence, Apple-confirmed forensic data, and months of OSINT mapping. All patterns match known NSO / Predator frameworks – but implemented via civilian, layered proxies using local BLE networks and cloud mirroring.


If you are in tech security and reading this: please help validate, replicate, and spread this structure. If it’s happening to me, it’s happening to others. Stay safe.


Nicetry!
#ShadowOS #BLEMeshExploit #XNUrootkit #PostVMRuntime #GameCenterHook #DFUrequired #CovertChannel #OSINTverified #APTstyle #OverTheAirRoot #MDMexploit #FindMyHijack #iCloudClone #RouterBackdoor #TR069abuse #SessionHijack #NSOstyle #HiddenESIM #LupeExploit #ShortcutsAbuse #FilesAppCloning #AppleTVpivot #SignalClone #ThreemaHijack #TelegramHook #ProtonVPNdivert #RootkitPersistence #FirmwareImplant #FireTVexploit #TwitchBackdoor #LunaAbuse #ActivityMonitorCrash #LogofailConfirmed #i386shadowVolume #MountHijack #OpenAIcovertTunnel #VodafoneSuperUser #HTTP401_482_500 #DFUrestoreEssential #iOSShadowRuntime #OverTheAirAPT #RobloxExploit #GameCenterPersistence
 
Last edited:
  • Haha
Reactions: BugeyeSTI

Forgot to mention – iCal / BLE Infection via Location-Based Triggers​


One overlooked but highly relevant method of persistent device tracking involves Apple Calendar (.ics) files combined with BLE-based location triggers.


These are not just normal calendar invites. In multiple observed cases:


  • .ics files silently imported location-based entries
  • BLE proximity was used to trigger actions from these entries
  • The system used Apple’s "Location Suggestions" and "Proactive Handoff" to activate FindMy-linked tracking or background hooks

Especially critical: Disable all “Location Suggestions” in Calendar settings. Also disable:


  • “Allow Calendar to use Location”
  • “Show Siri Suggestions in Calendar”
  • Shared/subscribed calendars (especially unknown .ics sources)

This vector was explicitly discussed with Apple forensic personnel, who confirmed that iCal location traces have appeared in device timelines during similar APT investigations. (used to re-hook)

It’s rarely documented – but real, repeatable, and silently effective.


If your calendar is compromised, your physical behavior becomes predictable – and your rebuild is already leaking.



Recovery & Reintegration Guide for ShadowOS / BLE / APT Victims​


(Full Field Protocol)
Compiled by Nicetry! – based on real-world infiltration, OSINT, and cross-system persistence


This is a practical, field-tested protocol based on 22+ months of infiltration, observation, and recovery attempts within a ShadowOS-style hybrid APT structure. The goal is not paranoia – it’s precision. This guide assumes persistence across cloud, device, social, and network layers – and offers a viable path forward for victims.




1. Device Recovery – Full Clean Rebuild​


  • Perform a DFU restore twice, offline, using a verified cable and clean system
  • Do not restore from iCloud or Time Machine
  • Best done in a neutral or public location, not your home or previous workspace
    → to avoid passive reinfection via nearby compromised IoT devices, BLE beacons, or rogue network signals

Immediately after setup:


  • Disable: iMessage, Find My, Apple Pay / Wallet, Auto Join Wi-Fi, Bluetooth
  • Activate Lockdown Mode (still imperfect, but reduces surface)
  • Create a new Apple ID on a clean device, with a fresh SIM from a different provider
  • Avoid any previously used credentials: Gmail, Proton, Hotmail, Spotify, PayPal, etc.



2. Router Hardening – Often Overlooked​


Attackers often use ISP equipment, VoIP protocols, or firmware exploits to regain presence via the network itself.


Minimal secure setup:


  • Disable TR-069, TR-064, TR-067 (remote provisioning APIs)
  • Disable UPnP and SIP ALG
  • Close SIP ports 5060–5061
  • Disable telephony recording/logging (WAV, MP3 etc.) – these files can carry payloads
  • Remove router user accounts (e.g. Fritzbox app users)
  • Disable remote access, WPS, guest networks
  • If possible: flash router firmware manually and verify integrity via hash



3. App Hygiene & Session Isolation​


  • Do not use apps like WhatsApp, Shortcuts, Automator, Files, or pre-installed scanner tools
  • These operate via cloud-coupled Apple frameworks and can be subverted remotely
  • Avoid installing any apps that have automation, sync, or background triggers enabled
  • Assume iCloud syncing = shadow mirroring = risk



4. Environmental Persistence & Profiling Risk​


Even with a new phone + account, going online in familiar environments (old apartment, friend’s home) may trigger passive re-identification


  • Known devices emit consistent BLE, Bonjour, and Wi-Fi signals
  • Attackers often pre-index the local environment for MACs, IMEIs, NFC, eSIM provisioning behavior

To avoid:


  • Set up your new ID away from known zones
  • Don’t log into familiar Wi-Fi networks – even once
  • Consider MAC spoofing + VPN during initial use



5. Social Layer – Hidden Reinfection Channel​


  • Do not import old contacts from iCloud or Gmail
  • Do not resume old Signal/Telegram accounts
  • Even close friends or partners may have been passively compromised (e.g. via contact hooks or device injection)

Many people may act as involuntary infection relays, especially if their devices were compromised during your attack period. This includes friends, partners, coworkers – even support staff or strangers who interacted with your network or physical space.


(GameCenter Multiplayer is a real issue...)


If you suspect reinfection via social contact, check their system logs for:


  • jetsamEvent → logs related to memory pressure or task termination, often preceding exploit activation
  • exec_resource → unsanctioned binary execution, often invisible to users
  • root:xnu inside a jetsamEventCritical proof of kernel-level injection or process hijack
  • wifimetrics, xp_amp_usage → signs of abnormal Wi-Fi events, even when Wi-Fi is disabled
  • bluetoothd → persistent or repeating BLE handshake activity, possible trigger behavior
  • intelligenceplatformd.cpu → runtime analytics activation outside normal usage
  • backboardwakeups, sirisearchfeedback → UI wake events or audio triggers without input

If root:xnu appears in jetsamEvent without corresponding crash or update, assume kernel-level compromise via post-VM rootkit or remote handler.


These patterns don’t just indicate compromise – they explain how reinfection persists silently through social proximity.




6. Desktop-Only Communication Model (Minimal Viable Online Life)​


  • Use a LAN-only desktop (Linux or hardened macOS) for all online interactions
  • No Wi-Fi, no Bluetooth, no auto-join anything
  • Run messaging apps like Signal on desktop only – avoid mobile logins
  • Disable notifications, background sync, and cloud features

If mobile is required:


  • Use clean “dumb” iPhones in airplane mode for reading or limited access only
  • Avoid inserting any previously known SIM cards



7. Real-World Considerations: Ethics, Abuse, and Responsibility​


Please remember:
Some forms of digital surveillance or behavioral tracking are ethically and legally justified – for example:


  • prevention of child abuse
  • national security risks
  • insider threats or critical infrastructure protection
  • or real-world violent intent

In such cases, even full-device access or deep metadata analysis may be warranted – if conducted with legal oversight, proportionality, and safeguards.


However, in most civilian scenarios, this threshold is not met.


→ What appears as “protective surveillance” often reveals itself as:


  • covert psychological pressure
  • full-device compromise without justification
  • or the ongoing digital tracking of individuals who pose no threat

Surveillance is not evil by nature — but it becomes abuse when the threat disappears and the control remains.
If there’s no real risk, but intrusion persists, the system has shifted from protection to domination.

If you're part of such a structure, ask yourself:


  • Who benefits?
  • Who is harmed?
  • And would you still do it if your name were attached to it?



8. Hardware Identity Exposure – IMSI & IMEI Re-Linking​


Even if you wipe the OS, create a new Apple ID, and change your passwords — you may still get tracked or re-infected if:


  • you use the same device hardware (same IMEI), or
  • you reinsert a previously known SIM card (same IMSI)

These identifiers are low-level, carrier-registered, and often known to the attacker if MDM-like access was ever active on your device.


Recommendation:


  • Set up your new Apple ID on a different physical device (if possible)
  • Use a completely fresh SIM, from a different provider
  • Do this in a clean physical environment, far from previously monitored locations
  • Avoid inserting any “burned” SIMs even for a second – they can trigger silent hooks

→ In real-world ops, attackers often run IMEI/IMSI correlation tables
→ Once a new account is linked to a known ID, the system sees you again — no matter how “new” you thought you were


This is the deepest trap of digital reintegration.
Break it by breaking the chain.



9. Final Thought – On Sadism, Survival & Purpose​


Some operations appear strategic.
Others reveal themselves to be purely sadistic – motivated by control, humiliation, and erasure.


If this applies to your case: you’re not imagining it.
You’re being tested – and documented – and possibly broken on purpose.


But:


  • you are not alone
  • your resistance is valid
  • and your clarity is a form of exit

Stay precise.
Stay human.
Stay rebuilding.

— Nicetry!
#ShadowOS #DFURequired #NoOldAccounts #RouterHardening #IMEIrelink #FindMyHijack #AppHygiene #ContactHooks #SessionPersistence #RealExitStrategy #HumanCenteredSecurity

 
  • Haha
Reactions: BugeyeSTI

Follow-Up: Contact Relays – The Invisible Infection Network


+ GameCenter as Persistent BLE Relay Layer


One subtle but deeply persistent infection vector in ShadowOS-type attacks is the social relay mechanism – especially through compromised contacts.


These are not just data leaks. They are behavioral hooks, designed to re-trigger location-based access, session persistence, or even BLE handshakes from previously trusted identities.

Key Observation (Confirmed in Multiple Cases):​


  • In several instances, specific contacts showed up with a gray, circular icon (no initials, no image) in apps like iMessage or Signal
  • These contacts did not need to interact – they functioned as passive mesh nodes
  • The presence of such contacts appears to indicate your currently monitored subnet, exposing the attacker’s active relay topology

→ Even if you switch devices, SIMs, or Apple ID – once such a relay device is nearby, your presence gets resolved via GameCenter or BLE-based hooks

GameCenter: A Covert Mesh Bridge Between Identities​


  • Apple’s GameCenter “Nearby Multiplayer” feature relies on:
    • BLE beacons
    • Bonjour (mDNS over Wi-Fi)
    • AppleID-linked service tokens
  • These mechanisms allow for device discovery via social graph, even outside your account scope

What this means:
→ If a known relay contact is nearby, and both devices have GameCenter enabled,
→ your device may get identified and re-linked via proximity alone, without direct interaction.


Think of it as an Apple-layer VPN, but for identity resolution –
the connection doesn’t go through you – it goes through who’s near you.




Persistent Game-Based Identity Inheritance?​


In one documented case, a Roblox account appeared in my Apple ID –
with a creation date from years prior and no user-side installation.


Other victims reported similar artifacts involving old online game accounts.
These accounts may:


  • Reside on Apple cloud infrastructure
  • Be linked to shared authentication tokens
  • Persist as invisible relay points or inherited session artifacts

→ This suggests longtail persistence – especially if MDM-like access once existed.

Contact relays don’t just leak data.
They rebuild covert identity channels
using your social environment as the carrier.

The mesh isn’t in the cloud.
It’s in the people you’ve touched – and the devices they carry.
#thxForBLEMeshExploit#ShadowOS #ContactRelays #GameCenterExploit #BLEmesh #greycontacts#AppleIDtracking #SessionPersistence #Rootxnu #FindMyHijack #NearbyMultiplayer #RelaySubnet #iMessageHook #BLEtrigger #JetsamEvent #InvisibleInfection #DeviceProximityLink

Stay sharp.
— Nicetry
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.