Can someone confirm if this is a serious system compromise?



Details:


I’ve encountered multiple suspicious behaviors across both my iPhone and MacBook Air, including:


• Device analytics showing unexpected activity and modified system logs


• Connectivity indicators (like “SOS” mode) persisting even in strong signal zones


• Repeated instances of app behavior inconsistent with official updates


• System UI and network behavior suggesting tampering or unauthorized configuration changes




This has been ongoing for some time, and I’ve collected extensive logs and evidence. My concern is this may be more than just a glitch—possibly a targeted system compromise involving both device and network layers.




I’m trying to determine if this is something others have experienced, and more importantly, if Apple engineers or advanced users can verify whether this indicates a serious breach.




Any technical insight would be appreciated. This has deeply affected my confidence in the security of my Apple devices.

iPhone 15, iOS 18

Posted on Apr 14, 2025 2:48 PM

Reply
Question marked as ⚠️ Top-ranking reply

Posted on Apr 14, 2025 5:48 PM

You will find no useful value in any analytic logs. They are not intended to user level interpreting of the data. They are useful to Apple Engineers when you have opened a Support Ticket at Apple for a specific issue and an Engineer notifies you that they would like to collect a specific log. They will not interpret the logs for you on request.


Relying on ChatGPT is always going to be problematic. Google trains their models on Social Media sites and specifically with a partnership with Reddit for their data. It is not unusual to find many posts on reddit claiming you have been hacked and the motivation is for upvotes and shares, not to provide any accurate information. You are not seeing results by Apple Engineers on what the analytics reveal, you are seeing what someone claims as they type away in their basement and ChatGPT takes that as factual information.


My recommendation is to stick with the issues you are having without any use of analytic logs. SOS is a lack of cell signal and the place to start is your cell provider. You have no bars showing for any cell coverage. They can use telemetry data to diagnose a condition with your service. It is possible it may be a hardware issue if there has been damage to the antenna and that can be diagnosed with an appointment at the Apple Store.


Problems with third party apps are best done with the App Developer. Are there bugs introduced in app updates? Absolutely, and those can only be resolved by the developer.


Apple is not here to review your post, so you cannot expect a response, but you can contact Apple directly here.

Contact Apple Support - Apple Support

11 replies
Sort By: 
Question marked as ⚠️ Top-ranking reply

Apr 14, 2025 5:48 PM in response to NomadicPolymath1

You will find no useful value in any analytic logs. They are not intended to user level interpreting of the data. They are useful to Apple Engineers when you have opened a Support Ticket at Apple for a specific issue and an Engineer notifies you that they would like to collect a specific log. They will not interpret the logs for you on request.


Relying on ChatGPT is always going to be problematic. Google trains their models on Social Media sites and specifically with a partnership with Reddit for their data. It is not unusual to find many posts on reddit claiming you have been hacked and the motivation is for upvotes and shares, not to provide any accurate information. You are not seeing results by Apple Engineers on what the analytics reveal, you are seeing what someone claims as they type away in their basement and ChatGPT takes that as factual information.


My recommendation is to stick with the issues you are having without any use of analytic logs. SOS is a lack of cell signal and the place to start is your cell provider. You have no bars showing for any cell coverage. They can use telemetry data to diagnose a condition with your service. It is possible it may be a hardware issue if there has been damage to the antenna and that can be diagnosed with an appointment at the Apple Store.


Problems with third party apps are best done with the App Developer. Are there bugs introduced in app updates? Absolutely, and those can only be resolved by the developer.


Apple is not here to review your post, so you cannot expect a response, but you can contact Apple directly here.

Contact Apple Support - Apple Support

Reply

Apr 14, 2025 6:06 PM in response to NomadicPolymath1

NomadicPolymath1 wrote:

Let’s set the record straight.

I’m not just “reading logs.” I’m compiling a forensic chain-of-custody trail—timestamped JSON from multiple SiriSearchFeedback logs showing irregular agent pairings, duplicate GUIDs, and impossible session overlap conditions. These aren’t Reddit rumors or AI hallucinations—they’re Apple-native diagnostic logs pulled from the iPhone analytics framework, formatted in JSON, and parsed using real tools—not opinions.

Yes you are reading logs and then looking for an explanation by running them through ChatGPT. That is the entire problem in that case. Yes, the ChatGPT data is trained on Reddit posts. The only thing that I have seen wrong is the SOS on your device, which is strictly a cellular condition whether that as from your provider or hardware on your device that has failed. That's it.


Reply

Apr 14, 2025 3:55 PM in response to NomadicPolymath1

NomadicPolymath1 wrote:



Details:

I’ve encountered multiple suspicious behaviors across both my iPhone and MacBook Air, including:

• Device analytics showing unexpected activity and modified system logs

• Connectivity indicators (like “SOS” mode) persisting even in strong signal zones

• Repeated instances of app behavior inconsistent with official updates

• System UI and network behavior suggesting tampering or unauthorized configuration changes



This has been ongoing for some time, and I’ve collected extensive logs and evidence. My concern is this may be more than just a glitch—possibly a targeted system compromise involving both device and network layers.



I’m trying to determine if this is something others have experienced, and more importantly, if Apple engineers or advanced users can verify whether this indicates a serious breach.



Any technical insight would be appreciated. This has deeply affected my confidence in the security of my Apple devices.

None of that indicates a breach.

There are no known hack/malware/spyware/virus for a non jailbroken devices.

SOS issue look here If you see SOS, No Service, or Searching on your iPhone or iPad - Apple Support

Reply

Apr 15, 2025 9:16 AM in response to NomadicPolymath1

If reported security issues have been ongoing for six months, a year, or longer, or potentially for over a decade as reported in this case, and presumably with multiple discussions with Apple and/or various postings with suggestions here or in other forums, or with other device or security or support providers or vendors, then the reported security issues — whatever those might be here — will not be resolved here, not by us.


Why won’t this get resolved here? There won’t be new or different suggestions offered here. Nothing new here that you have not already learned about, considered, and discarded or implemented as appropriate. We also don’t have access to your data and devices, and do not know your risks and exposures and the rest of your context, and posting that information here would be somewhere between inappropriate and inadvisable.


As for what has been posted in this thread, nothing here indicates any security issues.


Whether there are cellular issues with that SOS, either with the phone or the carrier or iOS?


The use of GPT text for technical analysis resource is ill-advised. GPTs are statistical tools that guess the next word based upon the previous words and big corpora of words. They’re statistical word salad, not wisdom.


Can ML be used to detect patterns of a breach? Sure, but you’ll need to train the ML with corpora of breached and unbreached devices. Those ML corpora are not going to be widely available. Data from Reddit chatter, sure.


Scanning telemetry data or scanning random JSON files is also searching for needles in haystacks, with an ever-increasing number of haystacks, without knowing what the needles might look like, or if there are any needles. And where various malware can simply delete the telemetry data. Can you potentially find evidence by examining telemetry data or at random JSON? Sure. Is it likely? Nope. Not without knowing what to look for, where and when to look, and all that also changes. Which means re-training the MLs, too. And means automated tooling to scan the massive amount of data involved.


As for the trust store, that’s protected the same as the rest of iOS, iPadOS, and macOS, and a breach there would mean the entire install is also breached. Here is an in-progress intro to that topic: Certificate Trust Store on iPhone, iPad, … - Apple Community


What to do? You’ll want and need to try a different approach. Whether that is learning about or contracting for formal data forensics, or learning about security implementations and exploitation, or consulting with specialists? Evidence-free threads are not going to advance your case toward the resolution you seek.


And more generally, the number of folks that want free forensics vastly exceeds the numbers and available time of those free forensics providers. Which means you’ll need to better characterize why your particular case is worth investigating.

Reply

Apr 14, 2025 4:05 PM in response to razmee209







Respectfully, I don’t believe this response adequately addresses the depth of the issue I’ve presented.




This is not a case of user error, general bugs, or standard network glitches. I’ve documented and analyzed:


• Device analytics showing unprompted activity and log inconsistencies


• Persistent SOS mode despite normal conditions and updated carrier firmware


• Certificate trust irregularities and mismatches in legal/copyright documents across synced devices


• “Throttled” server responses on apps like TikTok/Nextdoor, possibly indicating DNS or session-level interference


• Historical anomalies dating back over a decade, across multiple platforms




I’m not claiming malware in the traditional sense — this appears to involve selective traffic filtering, ghost network instances, or sandboxed environments that mimic normal system behavior while actively isolating or redirecting me.




If Apple engineers or anyone familiar with forensic-level diagnostics is monitoring this thread, I would appreciate an escalation path or private contact where I can submit logs, screenshots, and timestamped proof of these patterns.




This may not match conventional breach profiles — but it may reflect something even more serious.

Reply

Apr 14, 2025 5:42 PM in response to muguy







Respectfully, I’d like to challenge that conclusion.




The evidence I’ve shared isn’t just based on feeling—it includes structured SiriSearchFeedback logs, cross-referenced agent/app pairings (e.g. parsecd/visualintelligence and photos/parsecd), and anomalous session GUID behavior. These don’t align with typical iOS telemetry behavior. In fact, they match certain criteria Apple itself uses internally for flagging anomalies, including:


• Non-standard or duplicate user_guid fields


• App-agent mismatches not listed in any public or internal documentation


• Session logs with sudden timestamp shifts or inconsistencies in session_start




These are not typical user experience bugs or visual glitches. They’re artifacts that appear under compromise scenarios—either OS-level manipulation, injected telemetry spoofing, or lateral device instrumentation.




If you disagree, I genuinely welcome a line-by-line refutation of any extracted JSON I’ve posted. Let’s walk through it constructively. But blanket denial without forensic rebuttal—especially in a support environment—does a disservice to the wider Apple user base who may also be affected but unaware.




I’m documenting everything for public transparency, Apple escalation, and possible legal intake. If this ends up being a false positive, great. But so far, the patterns suggest otherwise—and I’d rather be cautious, informed, and methodical than prematurely dismissive.




Would you be open to reviewing the log structure directly?

Reply

Apr 14, 2025 5:49 PM in response to muguy







Respectfully, I’d like to challenge that conclusion.




The evidence I’ve shared isn’t just based on feeling—it includes structured SiriSearchFeedback logs, cross-referenced agent/app pairings (e.g. parsecd/visualintelligence and photos/parsecd), and anomalous session GUID behavior. These don’t align with typical iOS telemetry behavior. In fact, they match certain criteria Apple itself uses internally for flagging anomalies, including:


• Non-standard or duplicate user_guid fields


• App-agent mismatches not listed in any public or internal documentation


• Session logs with sudden timestamp shifts or inconsistencies in session_start




These are not typical user experience bugs or visual glitches. They’re artifacts that appear under compromise scenarios—either OS-level manipulation, injected telemetry spoofing, or lateral device instrumentation.




If you disagree, I genuinely welcome a line-by-line refutation of any extracted JSON I’ve posted. Let’s walk through it constructively. But blanket denial without forensic rebuttal—especially in a support environment—does a disservice to the wider Apple user base who may also be affected but unaware.




I’m documenting everything for public transparency, Apple escalation, and possible legal intake. If this ends up being a false positive, great. But so far, the patterns suggest otherwise—and I’d rather be cautious, informed, and methodical than prematurely dismissive.




Would you be open to reviewing the log structure directly?

Reply

Apr 14, 2025 5:53 PM in response to Mac Jim ID

Let’s set the record straight.




I’m not just “reading logs.” I’m compiling a forensic chain-of-custody trail—timestamped JSON from multiple SiriSearchFeedback logs showing irregular agent pairings, duplicate GUIDs, and impossible session overlap conditions. These aren’t Reddit rumors or AI hallucinations—they’re Apple-native diagnostic logs pulled from the iPhone analytics framework, formatted in JSON, and parsed using real tools—not opinions.




Here’s what concerns me:


• parsecd/visualintelligence paired with photos is not a documented Apple pairing.


• Repeating session_start values across different GUIDs are cryptographically improbable.


• Device shows root_installed: 0 but logs behavior consistent with instrumentation or spoofing.




That is not “nothing.” That is not “a hardware issue.” That is not a signal problem.




Telling users “Apple won’t read your logs” or “ignore what ChatGPT says” dodges the fact that something is wrong—and the pattern is repeatable. I’m not the only one raising these flags. This is a forensic pattern, not a one-off.




I invite anyone—engineers, developers, or Apple insiders—to refute the logs line by line. Show me documentation for the app-agent pairings. Show me why user_guid repetition across distinct incident IDs is “normal.” Otherwise, this kind of blanket dismissal is part of the problem—especially if it deters legitimate technical investigations.

Reply

Can someone confirm if this is a serious system compromise?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.