Sarai Hannah Ajai's Incident Reports Suspected Unauthorized Interference With Apple iPhone 17, Verizon Account Security Credentials, iMessage Activity, Verizon Orbic RC400L Device Observation, and Carrier Support Communications

 Incident Report

Subject

Suspected Unauthorized Interference With Apple iPhone 17, Verizon Account Security Credentials, iMessage Activity, Verizon Orbic RC400L Device Observation, and Carrier Support Communications

REDATED

Reporting Party: Sarai Hannah Ajai
Date of Incident: May 22, 2026
Location: *****, ***** ****** *****
Related Devices / Services: Apple iPhone 17, Verizon Wireless account, Verizon line ending in 6195, Verizon Orbic RC400L / Verizon_RC400L-7E Wi-Fi device, iMessage, Apple iCloud account, Apple Mac Mini M1, Verizon Technical Support
Related Individual Identified by Reporting Party: R****** B****, Apartment Unit 2**
Primary Verizon Support Number Reflected in Screenshots: +1 (800) 922-0204


I. Executive Summary

On May 22, 2026, I, Sarai Hannah Ajai, experienced another serious and distressing incident involving my Apple iPhone 17, Verizon account credentials, Apple iCloud account credentials, and Verizon-related device/security observations. Earlier that day, I changed multiple Verizon, Apple iPhone, iCloud, and Apple Mac Mini M1 credentials in an effort to secure my devices and account environment.

Shortly after making those security changes, I observed what I considered abnormal iPhone behavior while using the iMessage application. Specifically, while I was preparing to delete an Amazon message, I observed the iMessage screen move away or switch without my physical input. Because this occurred soon after multiple credential updates, I became concerned that my Apple iPhone 17 may again have been subject to unauthorized access, mirroring, cloning, session interference, or some other form of account/device compromise.

In response, I reviewed my Verizon Orbic RC400L / Verizon_RC400L-7E device environment, which I had been using as a practical observation tool to monitor connected-device behavior. Based on my observation, the device showed a connection count of two instead of one that I believed was inconsistent with only my Apple iPhone 17 being connected. I preserved Exhibit A as supporting evidence of the Verizon Orbic RC400L device involved in this observation.

I also report that after these security events, I heard statements from the neighboring apartment unit, 2**, which I attributed to Ms. R****** B****. The statements, as I heard them, referenced my Apple iPhone 17, my phone number, and alleged control or shared use of my device. I do not consent to Ms. B****, any tenant, or any other unauthorized person accessing, using, mirroring, cloning, controlling, sharing, or interfering with my Apple iPhone 17, Verizon account, iCloud account, phone number, personal communications, surveillance applications, or personal digital records.

Because of the severity of my concerns, I contacted Verizon Technical Support at approximately 1:48 PM. My call history and contact screenshots show Verizon-related call activity with +1 (800) 922-0204, including an outgoing call at approximately 1:48 PM lasting approximately fourteen minutes, an incoming call at approximately 2:03 PM lasting approximately six minutes, and additional missed/canceled call activity later that afternoon.

This report preserves my firsthand observations, the credential-change timeline, the Verizon support-call evidence, the reported neighbor statements, the effect on my safety and well-being, and the uploaded exhibits.


II. Background and Context

For more than one year, I have had recurring concerns regarding unauthorized access or attempted access to my Apple iPhone 17, Verizon account, Apple ecosystem, and related communications services. I have repeatedly changed passwords, PINs, passcodes, account credentials, and related security settings in an effort to maintain control over my personal devices and accounts.

On May 22, 2026, I again changed multiple security credentials across my Verizon and Apple account environment. These changes were made because I was concerned that my Apple iPhone 17 and Verizon account security environment were not remaining stable or private after prior credential updates.

I am documenting this incident because the sequence of events was unusual, disruptive, and alarming. I cannot independently determine the technical cause of every device or account event described in this report. However, I can state what I personally observed, what steps I took, what screenshots I preserved, what statements I heard, and how the incident affected me.


III. Credential Changes and Security Actions Taken

On May 22, 2026, I changed or updated the following credentials and security settings:

  1. Verizon account password — approximately 12:11 PM
  2. Verizon account PIN — approximately 12:11 PM
  3. Verizon voice PIN — approximately 12:12 PM
  4. Apple iPhone 17 passcode — approximately 12:13 PM
  5. Apple iPhone 17 Screen Time passcode — approximately 12:14 PM
  6. Verizon eSIM / eSIM-related PIN or security credential — approximately 12:16 PM
  7. Apple iCloud account credential/security setting — approximately 12:29 PM
  8. Apple Mac Mini M1 credential/security setting — approximately 12:43 PM

These actions were taken by me, as the lawful account holder and lawful owner/user of my personal devices, in an effort to protect my account, device, phone number, and communications.


IV. Incident Timeline

A. iMessage Screen Activity After Credential Changes

Date: May 22, 2026
Approximate Time: 1:51 PM

After completing the credential updates described above, I was using the iMessage application on my Apple iPhone 17. I was preparing to delete an Amazon  message. While I was viewing the iMessage application, I observed the app or screen move away without me intentionally touching or controlling the screen.

Because this event occurred shortly after I changed my Verizon, iPhone, iCloud, and Mac Mini credentials, I became concerned that my Apple iPhone 17 may have been subject to unauthorized remote control, mirroring, cloning, session interference, or another form of compromise.

I do not claim technical certainty as to the cause of this screen activity. I am documenting the event because it was unusual, occurred after multiple credential updates, and contributed to my belief that my device/account environment may not have remained secure.


B. Verizon Orbic RC400L / Verizon_RC400L-7E Observation

Date: May 22, 2026
Approximate Time: Shortly after the iMessage event

After observing the iMessage activity, I immediately checked my Verizon Orbic RC400L / Verizon_RC400L-7E device. I used the device because I wanted to observe whether the connected-device count appeared consistent with only my Apple iPhone 17 being connected.

Based on my observation at the time, the Verizon Orbic RC400L device displayed a connection condition that I believed showed two connected devices when I expected only one connected device. This caused me to believe that my Apple iPhone 17 may have been cloned, mirrored, or otherwise connected in an unauthorized way.

I preserved Exhibit A as supporting evidence of the Verizon Orbic RC400L device involved in this observation. I acknowledge that a later technical review would be necessary to determine exactly what the device was displaying, what devices were connected, whether the device count reflected a normal technical condition, or whether any unauthorized device activity occurred.


C. Reported Neighbor Statements From Unit 2**

Date: May 22, 2026
Approximate Time: After the credential changes and Verizon Orbic RC400L observation

After I changed my credentials and observed the device activity described above, I heard statements from the neighboring apartment unit, 2**, which I attributed to Ms. R******* B****. As I heard and understood the statements, Ms. B**** stated words to the effect of:

“Your iPhone 17 is everybody phone,”
“I did not give permission for you to use your iPhone 17,”
“You will not let me rub your back,” and
“I did not give out your phone number.”

I have never given Ms. B**** or any other tenant permission to access, use, control, mirror, clone, share, disclose, or interfere with my Apple iPhone 17, Verizon cellular number, Verizon account, iCloud account, iMessage, Ring application, surveillance camera access, or any personal digital account.

I also report that I previously allowed Ms. B**** to use my Samsung smartphone on or about October 1, 2023, after she came to my apartment unit, 2** door when she first moved into her apartment unit, 2** seeking food assistance and indicated she did not have money for cellular service to make a call so I let her used my Samsung smartphone. That isolated event did not give Ms. B**** permission to access, use, share, control, or interfere with any of my later devices, accounts, phone numbers, or personal communications.


D. Ring Application / Surveillance Evidence Concern

After hearing the reported statements from Unit 2**, I checked my iPhone 17 Ring application for possible video evidence. I observed that there did not appear to be video evidence of the verbal statements or harassment I reported hearing near my apartment unit, 2**.

Because of my broader concern that my Apple iPhone 17 may have been mirrored, cloned, or otherwise interfered with, I became concerned that surveillance-camera functionality, Ring application access, or video evidence may have been affected. I cannot independently prove from this observation alone that any video was deleted, disabled, altered, or blocked. However, the absence of expected video evidence increased my concern that my privacy, safety, and ability to preserve evidence were being affected.


E. Verizon Technical Support Contact

Date: May 22, 2026
Approximate Outgoing Call Time: 1:48 PM
Verizon Number Reflected in Screenshot: +1 (800) 922-0204

Because I was extremely upset and concerned about the integrity of my Verizon account and Apple iPhone 17, I contacted Verizon Technical Support at approximately 1:48 PM.

My preserved call-history screenshots reflect the following call activity with +1 (800) 922-0204:

  1. Outgoing Call — approximately 1:48 PM, lasting approximately 14 minutes
  2. Incoming Call — approximately 2:03 PM, lasting approximately 6 minutes
  3. Incoming Call — approximately 2:03 PM, missed
  4. Incoming Call — approximately 2:10 PM, missed
  5. Outgoing Call — approximately 2:51 PM, canceled
  6. Contact detail screen — approximately 2:52 PM, showing +1 (800) 922-0204 as a recent main contact

The call records are preserved in Exhibits B1, B2, and B3.

During the Verizon support interaction, I reported that my Apple iPhone 17 and Verizon account security credentials were repeatedly being compromised soon after I changed them. I also reported my concern that unauthorized individuals may be gaining access to my device, account, phone number, eSIM-related credentials, or account-security information.


V. Summary of Verizon Support Consultation

The AI-assisted Plaud transcript summary reflects that I contacted Verizon Technical Support regarding what I described as a severe and ongoing Apple iPhone 17 and Verizon account security issue.

The transcript summary reflects the following key points:

  1. I reported repeated unauthorized compromise concerns involving my Apple iPhone 17.
  2. I reported changing Verizon and Apple-related credentials frequently.
  3. I reported that the device/account environment appeared compromised again within a short period after security changes.
  4. I reported concern that unauthorized persons may be obtaining or using my Verizon account information.
  5. I reported concern that there may be an internal account-access issue involving a Verizon location or employee access to account information.
  6. I rejected a simple phone-number change as an adequate solution because I believe the underlying problem may involve access to account information, not only the phone number.
  7. I requested escalation to Verizon management, fraud/security review, or a specialized security department.

The transcript summary should be treated as a support-call summary, not a verbatim certified transcript, unless Verizon or another provider later confirms the call recording, account notes, timestamps, and employee actions.


VI. Behavioral and Safety-Impact Assessment

This section is not a psychological diagnosis of any person. I am not making a medical conclusion about Ms. B**** or any other tenant. I am documenting the behavioral pattern and safety impact from my perspective as the reporting party.

The reported statements and conduct are concerning because, if accurately documented, they show several contradictions relevant to my privacy and safety:

  1. Control contradiction: A neighbor allegedly made statements suggesting authority over my iPhone 17 while I am the lawful owner/user of the device and account.
  2. Consent contradiction: The alleged statement “I did not give permission for you to use your iPhone 17” is inconsistent with my legal right to use my own personal device, account, and phone number.
  3. Privacy contradiction: The alleged statement about my phone number is concerning because I have not knowingly given Ms. B**** or other tenants permission to use, disclose, distribute, or interfere with my cellular number.
  4. Safety contradiction: The reported statements occurred in the context of my concerns about device security, surveillance-camera access, and account control, which caused me to fear that my privacy and ability to document events may be compromised.
  5. Hostile-environment concern: The repeated statements I have reported regarding my biological sex, sexual orientation, and personal identity have caused me distress and may be relevant to a broader hostile-housing-environment or harassment analysis if further evidence supports the pattern.

From my perspective, these statements and events are not ordinary neighbor noise or ordinary disagreement. They involve alleged claims about my personal device, my phone number, my privacy, and my identity. I am documenting them because they affect my sense of safety, privacy, and ability to live without intimidations or interferences.


VII. Legal Significance and Potentially Relevant Statutes

This section is not a final legal conclusion. It identifies legal frameworks that may be relevant if a later technical, carrier-side, forensic, or law-enforcement review confirms unauthorized access, account misuse, interception, credential misuse, or telecommunications-account irregularities.

1. Computer Fraud and Abuse Act — 18 U.S.C. § 1030

The Computer Fraud and Abuse Act includes provisions addressing unauthorized access to protected computers and conduct that causes damage or loss through unauthorized access or transmission-based activity. If later review shows that any person accessed, controlled, altered, interfered with, or obtained information from my Apple iPhone 17, Apple Mac Mini M1, Apple account environment, or related device/session data without authorization, this statute may be relevant. (U.S. Code)

2. Stored Communications Act — 18 U.S.C. § 2701

The Stored Communications Act addresses unauthorized access to a facility through which electronic communication service is provided where the conduct obtains, alters, or prevents authorized access to electronic communications in storage. If later review shows unauthorized access to iMessage content, stored account communications, iCloud-linked records, carrier account records, or session-related communications, this statute may be relevant. (U.S. Code)

3. Federal Wiretap Act / Interception of Communications — 18 U.S.C. § 2511

Federal law prohibits intentional interception, attempted interception, or procurement of another person to intercept wire, oral, or electronic communications unless legally authorized. If later review shows that calls, iMessages, account sessions, carrier communications, or device traffic were intercepted, redirected, monitored, or captured without authorization, this statute may be relevant. (Legal Information Institute)

4. Fraud and Related Activity Involving Identification Information — 18 U.S.C. § 1028

Federal law addresses fraud-related activity involving identification documents, authentication features, and identifying information. If later review shows that my identifying information, authentication features, account credentials, device-linked identifiers, or account profile information were used without lawful authority, this statute may be relevant. (U.S. Code)

5. Aggravated Identity Theft — 18 U.S.C. § 1028A

Aggravated identity theft applies where a person knowingly transfers, possesses, or uses another person’s means of identification without lawful authority during and in relation to certain predicate felony offenses. If later investigation confirms that my identifying information or account credentials were used in connection with a qualifying federal offense, this statute may be relevant. (Legal Information Institute)

6. Fraud and Related Activity in Connection With Access Devices — 18 U.S.C. § 1029

Federal access-device law may be relevant where unauthorized access devices, credentials, or account-access mechanisms are used with fraudulent intent. If later review shows misuse of PINs, account access credentials, eSIM credentials, or other access mechanisms connected to my Verizon account or related services, this statute may warrant review. (Legal Information Institute)

7. Telecommunications Privacy / Customer Proprietary Network Information — 47 U.S.C. § 222

Federal telecommunications law requires telecommunications carriers to protect customer proprietary network information. If later review shows irregular access to my Verizon customer account information, account notes, PIN-related information, call records, device-change records, eSIM activity, or carrier-side account security details, this framework may be relevant to a provider-side investigation. (U.S. Code)


VIII. Effect on Me

This incident caused me substantial fear, anger, distress, and disruption. I had just changed multiple credentials across my Verizon account, Apple iPhone 17, Apple iCloud account, and Apple Mac Mini M1. Shortly afterward, I observed iMessage activity that appeared abnormal to me, reviewed my Verizon Orbic RC400L device, and heard statements from a neighboring apartment unit, 2**  that I understood as referring to my phone, my phone number, and alleged control over my device.

I felt that my privacy, personal safety, communications, identity, and ability to document evidence were being affected. I also felt that my right to use my own personal device and phone number was being challenged or interfered with by people who have no legal authority over my devices, accounts, or personal communications.

The incident also interfered with my ability to work, concentrate, and maintain a stable personal environment.


IX. Formal Statement

I, Sarai Hannah Ajai, state that on May 22, 2026, at my apartment located at **** **** ***. *., Unit 2**, *****, ***** ****** *****, I changed multiple Verizon, Apple iPhone 17, Apple iCloud, and Apple Mac Mini M1 credentials in an effort to secure my personal account and device environment.

After those credential changes, I observed abnormal iMessage activity on my Apple iPhone 17, checked my Verizon Orbic RC400L / Verizon_RC400L-7E device, and observed a connected-device condition that caused me concern. I also heard statements from Unit 2**, which I attributed to Ms. R******* B****, referencing my Apple iPhone 17, phone number, and alleged permission or control over my device.

I contacted Verizon Technical Support at approximately 1:48 PM, and I preserved screenshots showing Verizon-related call activity with +1 (800) 922-0204. I am preserving this report and the attached exhibits as a factual record of my firsthand observations, my security actions, my support-call activity, and the effect this incident had on my privacy, safety, and well-being.

I do not claim technical certainty regarding the cause of every event described in this report. I request that any appropriate service provider, investigator, legal counsel, regulator, or law-enforcement reviewer treat this report as a preservation-oriented record requiring further technical review, carrier-log review, device forensic review, account-access review, and evidence preservation.


X. Uploaded Exhibits / Supporting Evidence

Exhibit A

File: Exhibit A.jpeg
Description: Photograph of Verizon Orbic RC400L / Jetpack-related device screen. The reporting party states this device was used to review connected-device behavior after the Apple iPhone 17 concern.

Exhibit B1

File: Exhibit B1.jpg
Description: Apple iPhone call/contact screen showing +1 (800) 922-0204, call-history panel, and missed-call information at approximately 2:10 PM. The screen also states that calls with a checkmark have been verified by the carrier.

Exhibit B2

File: Exhibit B2.jpg
Description: Apple iPhone call-history screenshot showing Verizon-related call activity with +1 (800) 922-0204, including outgoing, incoming, missed, and canceled call entries between approximately 1:48 PM and 2:51 PM.

Exhibit B3

File: Exhibit B3.jpg
Description: Apple iPhone contact/details screen showing +1 (800) 922-0204 as a recent main contact, with standard contact options and call interface details.

Additional Uploaded Image

File: image.png
Description: Additional uploaded image preserved with the incident materials. The reporting party may later clarify its evidentiary purpose if needed.


XI. Preservation Request

I request preservation of all records potentially related to this incident, including but not limited to:

  1. Verizon account-access logs
  2. Verizon customer-service call notes and recordings
  3. Verizon employee/account-view access logs
  4. eSIM activation, change, or profile-management records
  5. Account PIN/password/voice PIN change records
  6. Device connection and account-authentication logs
  7. Apple ID, iCloud, iMessage, and Apple device security logs available through lawful channels
  8. Ring application access logs and video-retention records
  9. Any relevant apartment-management or surveillance records
  10. Any communications or records showing unauthorized access to my phone number, account, device, or personal identifying information

Respectfully submitted,

Sarai Hannah Ajai
Date: May 22, 2026













Comments