Labels

Sarai Hannah Ajai Formal Incident Report Regarding Verbal Threats, Identity-Related Harassment, Threatened Taking of Personal Effects, Apple iPhone 17 Screen Time Passcode Interference, and Verizon Orbic RC400L / Rayhunter Device-Count Irregularity

 Formal Incident Report Regarding Verbal Threats, Identity-Related Harassment, Threatened Taking of Personal Effects, Apple iPhone 17 Screen Time Passcode Interference, and Verizon Orbic RC400L / Rayhunter Device-Count Irregularity

Redacted

Prepared by: Sarai Hannah Ajai
Location: *****, ***** ******
Residence Reference: Apartment Unit 2**
Incident Dates: May 15, 2026 and May 16, 2026
Primary Device: Apple iPhone 17
Carrier / Account: Verizon Wireless
Monitoring Device: Verizon Orbic RC400L mobile hotspot with Rayhunter environment
Wi-Fi Network Referenced: Verizon-RC400L-7E
Related Account: Apple iCloud / Apple ID account associated with Apple iPhone 17
Possible Location of Suspected Speaker: Building 1, likely Apartment 3**, **20 20th ***. S., *****, ***** ****** *****
Purpose of Report: Personal record, property-management notice, Verizon escalation, Apple security review, FTC/FCC complaint support, attorney review, law-enforcement review, housing-rights review, and evidence preservation

I. Executive Summary

I, Sarai Hannah Ajai, am preparing this formal incident report to document a serious sequence of events occurring on May 15, 2026 and May 16, 2026, involving verbal threats, identity-related harassment, threatened taking of my personal effects, suspected interference with my Apple iPhone 17 Screen Time passcode, and a later Verizon Orbic RC400L / Rayhunter device-count irregularity.

On May 15, 2026, at approximately 9:30 PM, I was sitting at my bedroom desk writing JavaScript code for the VaultInbox.Cloud web application when I heard a woman shouting from a patio door. The statements appeared to be directed toward me because they referenced items that I personally carry, including my backpack and Lands’ End tote bag, which contain my personal devices, personal effects, and business documentations. The speaker also made hostile statements concerning my sex, identity, refusal to communicate with certain persons, refusal to surrender control of my identity, and businesses I created.

After the woman stopped speaking, I got up from my desk and looked out of my bedroom window. I saw an African American heavy-set woman standing on the patio of Building 1, most likely at Apartment 3**, located at **20 20th ***. *., *****, ***** ****** *****. I do not know this woman as an acquaintance, I have never communicated with her, and I do not live in Building 1.

On May 16, 2026, at approximately 12:16 PM, I logged into my bank account after receiving a bank one-time passcode sent to my Apple iPhone 17 iMessages app. I used my iPhone 17 Screen Time passcode to unlock the iMessage app without apparent interference. A few minutes later, at approximately 12:20 PM, I noticed an Amazon reminder text message in iMessage and attempted to use my four-digit Screen Time passcode, 7457, to unlock the iMessage app. The passcode failed repeatedly, even though I had updated the Screen Time passcode from 8515 to 7457on May 15, 2026, at approximately 5:10 PM. After repeated failed attempts, I was locked out of Screen Time passcode access for five minutes. This lockout is preserved as Exhibit A.

On the same date, at approximately 1:03 PM, I checked my Verizon Orbic RC400L Rayhunter device, and it displayed two connected devices on the Verizon-RC400L-7E Wi-Fi network. Only one device should have been connected: my Apple iPhone 17. This is preserved as Exhibit C.

This report does not state as a final forensic conclusion that my Apple iPhone 17 was definitely mirrored, cloned, remotely accessed, or unlawfully controlled. Instead, this report documents the observed facts, the threats I heard, the timing of the Screen Time passcode failure, the apparent device-count irregularity, and my concern that the verbal threats and device interference may be connected.

The strongest careful conclusion is:

On May 15 and May 16, 2026, I experienced a pattern involving identity-related verbal threats, threatened taking of my personal effects, hostile statements concerning my sex and identity, Apple iPhone 17 Screen Time passcode failure shortly after a successful iMessage access event, and a Verizon Orbic RC400L connected-device display showing two connected devices when only one device was expected. These events should be preserved and reviewed by Apple, Verizon, property management, law enforcement, or a qualified technical reviewer.

II. Background and Context

I reside in Apartment Unit 2** in *****, ***** ******. I am the lawful owner and user of my personal effects, electronic devices, identity credentials, business documentations, and personal accounts.

I regularly carry a backpack and a Lands’ End tote bag containing personal devices, personal effects, and business documentations. These items are not located inside the suspected speaker’s apartment unit 3**. They do not belong to the suspected speaker. They are not property of any tenants in Building 1. They are my personal effects.

I am also the creator and developer of multiple business and technology projects, including VaultInbox.Cloud. On May 15, 2026, I was actively writing JavaScript codes for the VaultInbox.Cloud web application in my IDE editor when I heard the woman shouting from her patio area.

The statements I heard were alarming because they included:

  1. sexualized verbal harassment;
  2. hostile statements concerning my biological female sex;
  3. threats or implied threats regarding my backpack and Lands’ End tote bag;
  4. statements suggesting that my businesses are not mine;
  5. statements concerning control over my identity;
  6. statements about my refusal to communicate with persons I do not know;
  7. a later direct threat to “shoot” me if I did not surrender my identity, backpack, and tote bag.

This report is prepared because the combined events created a serious concern involving personal safety, identity security, personal-property safety, housing safety, and possible interferences with my personal Apple and Verizon devices.

III. Persons and Locations Involved

A. Reporting Individual

Name: Sarai Hannah Ajai
Residence Reference: Apartment Unit 2**
Role in Incident: Reporting individual, lawful owner of personal effects, Apple iPhone 17, Apple iCloud account, Verizon account, and business documentations referenced in this report.

B. Suspected Speaker

The suspected speaker is described as an African American heavy-set woman observed standing on the patio of Building 1, most likely Apartment 3**, located at **20 20th ***. *., *****, ***** ****** *****.

This identification is based on my observation from my bedroom window after the May 15, 2026 verbal statements stopped. I do not know the woman personally, I have not communicated with her, and I do not live in Building 1.

C. Location of First Verbal Incident

The first verbal incident occurred while I was inside Apartment Unit 2**, seated at my bedroom desk. The shouting appeared to come from a patio area in Building 1, likely Apartment 3**.

D. Location of Second Verbal Incident

The second verbal incident occurred on May 16, 2026, while I was again inside Apartment Unit 2**. I heard the woman shouting from inside or near Apartment 3** with the patio door open loudly enough for me to hear the statements.

IV. Devices, Accounts, and Personal Effects Involved

A. Apple iPhone 17

My Apple iPhone 17 is my personal device. It is associated with my Apple iCloud account and Verizon account. It received the bank OTP code at approximately 12:16 PM on May 16, 2026, and it later showed repeated Screen Time passcode failure messages at approximately 12:20 PM.

B. Apple iCloud / Apple ID Account

My Apple iCloud account is associated with the Apple iPhone 17. Due to continuing device-security concerns, I have felt legally and practically forced to change my Apple iCloud account password frequently, including daily, to protect access to my device and personal accounts.

C. Screen Time Passcode

The Screen Time passcode at issue was 7457. I updated it from 8515 to 7457 on May 15, 2026, at approximately 5:10 PM. On May 16, 2026, at approximately 12:20 PM, the passcode 7457 failed repeatedly when I attempted to unlock access to the iMessage app after receiving an Amazon reminder text message.

D. Verizon Account and Device Number

My Apple iPhone 17 is associated with my Verizon account. I question whether an unknown person or device may have interfered with, mirrored, cloned, or otherwise affected the Apple iPhone 17 device number associated with my Verizon account.

E. Verizon Orbic RC400L / Rayhunter Device

At approximately 1:03 PM on May 16, 2026, my Verizon Orbic RC400L Rayhunter device displayed two connected devices on the Verizon-RC400L-7E Wi-Fi network, even though only one device should have been connected: my Apple iPhone 17.

F. Backpack and Lands’ End Tote Bag

The backpack and Lands’ End tote bag referenced by the woman are my personal effects. They contain personal devices, personal effects, and business documentation. I do not consent to any person taking, interfering with, searching, accessing, controlling, or claiming ownership over those items.

V. May 15, 2026 Incident Narrative — Patio Shouting and Threats Regarding Identity, Personal Effects, and Businesses

On May 15, 2026, at approximately 9:30 PM, I was sitting at my bedroom desk writing JavaScript codes for the VaultInbox.Cloud web application. While working in my IDE editor, I heard a woman shouting from her patio door about my well-being and safety.

The woman shouted the following statement, quoted here because it is relevant to the nature of the incident:

“YOU HAVE REFUSED TO SUCK COCK AND YOU REFUSE TO BE A MALE FROM BIRTH. I AM SICK OF YOU. YOU REFUSE TO SPEAK TO US, AND YOU ARE ALWAYS WALKING AROUND WITH YOUR BACKPACK AND TOTE BAG AND REFUSE TO LEAVE IT IN YOUR APARTMENT, AND I AM GOING TO FIND A WAY TO TAKE THOSE ITEMS FROM YOU SOMEHOW AND THOSE COMPANIES YOU HAVE CREATED ARE NOT YOURS THEY ARE MINES BECAUSE YOU HATE BEING AROUND BLACK PEOPLE WHO WANT TO TAKE CONTROL OF IDENTITY.”

After the woman stopped speaking, I got up from my desk and looked out of my bedroom window. I observed an African American heavy-set woman standing on the patio of Building 1, most likely at Apartment 3**, located at **20 20th ***. *., *****, ***** ****** *****.

At first, I questioned who the woman was referring to because I am the only person I know who regularly carries both a backpack and a Lands’ End tote bag containing my personal devices, personal effects, and business documentations. I also questioned why my personal items would be any concern of hers, because those items are not located in her apartment unit, she is not responsible for them, and they belong to me.

I did not respond to the woman. I did not engage her. I ignored the rest of the statements and returned to focusing on the VaultInbox.Cloud web application in my IDE editor.

What is extremely disturbing is that I do not know this woman as an acquaintance, I have never communicated with her, and I do not live in Building 1. The statements did not make reasonable sense to me because they appeared to concern my personal identity, my sex, my personal effects, and my technology/business work even though I have no relationship with the speaker.

VI. May 16, 2026 Incident Narrative — Bank OTP, iMessage Access, Second Shouted Threat, Screen Time Passcode Failure, and Five-Minute Lockout

On May 16, 2026, at approximately 12:16 PM, I logged into my bank account after receiving a bank OTP code sent to my Apple iPhone 17’s Messages app. I used my iPhone 17’s Screen Time passcode to unlock the iMessage app without any apparent interference.

Shortly after that successful iMessage access, I again heard the woman shouting from inside or near Apartment 3** with her patio door open loudly enough for me to hear her. She stated:

“I AM NOT PLAYING WITH YOU AT ALL. WE WILL SHOOT YOU DOWN IF YOU DO NOT GIVE US YOUR IDENTITY, BACKPACK, AND LANDS’ END TOTE BAG.”

I ignored the threat and did not communicate with the woman. I also did not consent to give any person my identity, backpack, Lands’ End tote bag, Apple iPhone 17, Apple iCloud account, Verizon account, or business documentation.

At approximately 12:20 PM, I received an Amazon reminder text message in my iMessage app. I attempted to use my Apple iPhone 17 four-digit Screen Time passcode, 7457, to unlock the app. I received an error message stating:

“1 Failed Passcode Attempt.”

I entered the same four-digit passcode, 7457, again and received another error message stating:

“2 Failed Passcode Attempts.”

This happened four more times. I was then locked out of my iPhone 17 Screen Time passcode access for five minutes. This lockout is preserved as Exhibit A.

This was highly concerning because I had updated my Screen Time passcode from 8515 to 7457 on May 15, 2026, at approximately 5:10 PM. I had not left my apartment unit 2**, and I had not communicated with anyone using my Apple iPhone 17.

The fact that the passcode worked at approximately 12:16 PM for the bank OTP access but failed repeatedly at approximately 12:20 PM after the Amazon reminder text message is a key timing issue that should be preserved for review.

VII. May 16, 2026 Incident Narrative — Verizon Orbic RC400L / Rayhunter Device-Count Irregularity

At approximately 1:03 PM on May 16, 2026, I checked my Verizon Orbic RC400L Rayhunter device. The device showed that two devices were connected to the Verizon-RC400L-7E Wi-Fi network.

Only one device should have been connected to that Wi-Fi network: my Apple iPhone 17.

The Orbic RC400L Rayhunter display showing two connected devices is preserved as Exhibit C.

This device-count issue is concerning because it occurred shortly after:

  1. the woman made a direct threat involving my identity, backpack, and Lands’ End tote bag;
  2. I successfully used my Screen Time passcode to access iMessage at approximately 12:16 PM;
  3. the same Screen Time passcode failed repeatedly at approximately 12:20 PM;
  4. my Apple iPhone 17 locked me out of Screen Time passcode access for five minutes;
  5. I had not left Apartment Unit 2**;
  6. I had not communicated with anyone using my Apple iPhone 17.

The device-count display does not, by itself, prove cloning, mirroring, remote control, or unauthorized access. However, it is significant enough to preserve because only one device was expected to be connected, and the Orbic RC400L Rayhunter device showed two connected devices.

VIII. Timeline and Minute-by-Minute Analysis

Date / Approx. Time

Event

Time Relationship

Significance

May 15, 2026 — 5:10 PM

I updated my Apple iPhone 17 Screen Time passcode from 8515 to 7457.

Baseline security event

Establishes the known Screen Time passcode before the incidents.

May 15, 2026 — 9:30 PM

I heard the woman shouting from a patio door while I was writing JavaScript codes for VaultInbox.Cloud.

Approx. 4 hours 20 minutes afterScreen Time passcode update

First reported verbal incident involving identity, sex, backpack, tote bag, and businesses.

May 16, 2026 — 12:16 PM

I logged into my bank account and received a bank OTP code through iMessage. I used the Screen Time passcode successfully to access iMessage.

Approx. 19 hours 6 minutes afterScreen Time passcode update

Shows that iMessage access using the passcode appeared to work at this time.

May 16, 2026 — shortly after 12:16 PM

I heard the woman shout a direct threat: “WE WILL SHOOT YOU DOWN IF YOU DO NOT GIVE US YOUR IDENTITY, BACKPACK, AND LANDS’ END TOTE BAG.”

Same time window as bank/iMessage access

Establishes direct threat and identity/personal-property demand.

May 16, 2026 — 12:20 PM

I received an Amazon reminder text message and attempted to unlock iMessage using Screen Time passcode 7457. The passcode failed repeatedly.

Approx. 4 minutes after successful bank/iMessage access

Key device-security irregularity.

May 16, 2026 — approx. 12:20 PM

iPhone displayed failed passcode attempts and then a five-minute lockout.

Same event window

Preserved as Exhibit A.

May 16, 2026 — 1:03 PM

Verizon Orbic RC400L Rayhunter showed two connected devices on Verizon-RC400L-7E, when only one device was expected.

Approx. 43 minutes afterScreen Time passcode failure

Preserved as Exhibit C; requires technical review.

Timing Interpretation

The timing is important because the Apple iPhone 17 Screen Time passcode appeared to work at approximately 12:16 PM but then failed repeatedly at approximately 12:20 PM, only about four minutes later.

The Verizon Orbic RC400L Rayhunter device-count irregularity occurred at approximately 1:03 PM, about 43 minutes after the Screen Time passcode failure and five-minute lockout.

This timing does not prove the cause of the passcode failure or the device-count irregularity. However, the sequence is significant because the verbal threat, passcode failure, lockout, and two-device display occurred within a closely connected time period.

IX. Technical Concern Regarding Screen Time Passcode Interference

Based on my observation, the Screen Time passcode 7457 should have worked because I had updated it on May 15, 2026, at approximately 5:10 PM, and I had used it successfully at approximately 12:16 PM on May 16, 2026.

At approximately 12:20 PM, the same passcode failed repeatedly. This caused a lockout for five minutes.

In my view, one possible explanation requiring technical review is that my Apple iPhone 17 Screen Time passcode may have been changed or reset without my knowledge or consent. I am concerned that this could have occurred through:

  1. unauthorized access to my Apple iCloud account;
  2. unauthorized knowledge or use of my Apple ID email address;
  3. unauthorized knowledge or use of my Apple iCloud password;
  4. a Screen Time passcode reset process involving the “Turn Off Passcode” screen and “Forgot Passcode?” option;
  5. device mirroring or device cloning;
  6. unauthorized trusted-device access;
  7. unauthorized Apple ID session access;
  8. Apple iPhone 17 device-number or Verizon-line interference;
  9. another unknown technical condition affecting Screen Time passcode behavior.

This report does not determine which explanation is correct. It preserves the issue for Apple, Verizon, law enforcement, or a qualified technical reviewer.

X. Technical Concern Regarding Verizon Orbic RC400L / Rayhunter Showing Two Connected Devices

At approximately 1:03 PM on May 16, 2026, my Verizon Orbic RC400L Rayhunter device displayed two connected devices on the Verizon-RC400L-7E Wi-Fi network.

The expected connected-device count was:

1 connected device — my Apple iPhone 17 only.

The observed connected-device count was:

2 connected devices displayed by the Verizon Orbic RC400L Rayhunter device.

The discrepancy should be preserved because it may indicate one or more possible technical conditions, including:

  1. unknown second Wi-Fi client;
  2. stale connected-device display;
  3. prior DHCP lease still appearing;
  4. Apple Private Wi-Fi Address behavior;
  5. duplicate Apple iPhone 17 device-name entry;
  6. router display delay;
  7. Verizon Orbic interface condition;
  8. Rayhunter display or monitoring anomaly;
  9. unauthorized Wi-Fi association;
  10. device mirroring or cloning indicator;
  11. Apple iCloud / Apple ID account irregularity;
  12. Verizon account, eSIM, SIM, device number, or device-authentication irregularity.

This report does not state as a final conclusion that the second displayed device was definitely unauthorized. It states that only one device should have been connected and that the display showed two devices, which requires review.

XI. Relationship Between Verbal Threats and Device Concerns

The verbal threats are relevant to the technical concerns because the woman’s statements specifically referenced:

  1. my identity;
  2. my refusal to communicate;
  3. my backpack;
  4. my Lands’ End tote bag;
  5. my personal effects;
  6. the companies I created;
  7. taking control of my identity;
  8. a direct threat to shoot me if I did not give up my identity and personal items.

The device concerns are relevant because, within the same general timeframe:

  1. my Apple iPhone 17 received and processed a bank OTP through iMessage;
  2. my Screen Time passcode worked at approximately 12:16 PM;
  3. the same Screen Time passcode failed repeatedly at approximately 12:20 PM;
  4. I was locked out for five minutes;
  5. the Verizon Orbic RC400L Rayhunter displayed two connected devices at approximately 1:03 PM.

The combined pattern created a serious concern that the verbal threats and technical irregularities may be connected. However, further technical review is needed before any final determination can be made.

XII. Housing and Personal-Safety Impact

The statements shouted by the woman have created a hostile and intimidating housing environment. I do not know this woman, I have not communicated with her, and I do not live in Building 1.

The May 15 and May 16 statements caused me to feel unsafe because they involved:

  1. sexualized harassment;
  2. identity-related hostility;
  3. statements concerning my biological female sex;
  4. threats or implied threats against my personal effects;
  5. claims concerning businesses I created;
  6. statements suggesting control over my identity;
  7. a direct threat to shoot me if I did not give up my identity, backpack, and Lands’ End tote bag.

These statements affected my well-being and interfered with my ability to feel secure inside my own apartment unit 2** while working on my web application.

XIII. Legal Significance and Review Issues

This report is prepared for documentation and review. The conduct described may be relevant to several categories of concern, including:

  1. Threat of violence: The statement “WE WILL SHOOT YOU DOWN” should be treated as a direct safety concern.
  2. Threatened taking of personal property: The statement about finding a way to take my backpack and Lands’ End tote bag should be preserved as a threat concerning my personal effects.
  3. Identity-related intimidation: The statements about taking control of my identity should be preserved as identity-related harassment and possible coercion.
  4. Sexualized harassment: The May 15 statement contained explicit sexualized language directed toward me.
  5. Sex-based hostility: The statements concerning my refusal “to be a male from birth” should be preserved as hostile sex-based language.
  6. Business-ownership interference: The statement that the companies I created are “not yours” should be preserved because it referenced my business and development work.
  7. Possible electronic-device interference: The Screen Time passcode failure and Verizon Orbic two-device display should be reviewed by Apple, Verizon, and a qualified technical reviewer.
  8. Hostile housing environment: The repeated shouting, threats, identity demands, and device-related concerns may be relevant to a housing-safety review.

This section is not presented as a final legal conclusion. It identifies issues requiring preservation and review.

XIV. Exhibit A — Apple iPhone 17 Screen Time Passcode Five-Minute Lockout

Exhibit A is a screenshot showing the Apple iPhone 17 Screen Time passcode lockout after repeated failed attempts using the four-digit passcode 7457.

Exhibit A Relevance

Exhibit A is relevant because it documents that my Apple iPhone 17 locked me out of Screen Time passcode access for five minutes on May 16, 2026, shortly after I had successfully accessed iMessage for a bank OTP at approximately 12:16 PM.

Exhibit A Limitation

Exhibit A shows the lockout result. It does not, by itself, prove how the passcode failed, whether the passcode was changed, whether the device was accessed by another person, or whether there was a technical issue. It should be reviewed alongside Apple account records, Screen Time reset records, trusted-device records, and device logs where available.

XV. Exhibit B — Apple iPhone 17 Screen Time “Turn Off Passcode” / “Forgot Passcode?” Reset Path

Exhibit B is a screenshot or documentation reference concerning the Apple iPhone 17 Screen Time passcode reset path, including the “Turn Off Passcode” screen and “Forgot Passcode?” option.

Exhibit B Relevance

Exhibit B is relevant because I am concerned that an unauthorized person may have used or attempted to use the Screen Time passcode reset process by entering my email address and Apple iCloud account password.

Exhibit B Limitation

Exhibit B does not prove that an unauthorized reset occurred. It identifies a possible technical path that should be reviewed by Apple or a qualified device-security reviewer.

XVI. Exhibit C — Verizon Orbic RC400L / Rayhunter Display Showing Two Connected Devices

Exhibit C is a photograph or screenshot showing that the Verizon Orbic RC400L Rayhunter device displayed two connected devices on the Verizon-RC400L-7E Wi-Fi network at approximately 1:03 PM on May 16, 2026.

Exhibit C Relevance

Exhibit C is relevant because only one device should have been connected to the network: my Apple iPhone 17. The displayed count of two connected devices are therefore a device-count irregularity requiring review.

Exhibit C Limitation

Exhibit C should be interpreted carefully. It appears to show two connected devices, but a complete technical determination would require:

  1. Orbic admin connected-client records;
  2. device names;
  3. IP addresses;
  4. MAC addresses or Apple private Wi-Fi addresses;
  5. DHCP lease times;
  6. timestamps;
  7. whether one entry was stale;
  8. whether the second entry remained after disconnecting the iPhone;
  9. whether the count changed after rebooting the Orbic;
  10. whether the count changed after changing the Orbic Wi-Fi password;
  11. Rayhunter logs from the same time period.

XVII. Evidence Preservation Statement

I am preserving the following evidence and notes:

  1. Exhibit A: Apple iPhone 17 Screen Time passcode five-minute lockout screenshot.
  2. Exhibit B: Apple iPhone 17 Screen Time “Turn Off Passcode” / “Forgot Passcode?” reset-path screenshot or documentation reference.
  3. Exhibit C: Verizon Orbic RC400L / Rayhunter display showing two connected devices.
  4. Notes documenting that I updated my Screen Time passcode from 8515 to 7457 on May 15, 2026, at approximately 5:10 PM.
  5. Notes documenting the May 15, 2026 verbal incident at approximately 9:30 PM.
  6. Notes documenting the May 16, 2026 bank OTP / iMessage access at approximately 12:16 PM.
  7. Notes documenting the May 16, 2026 direct threat made shortly after 12:16 PM.
  8. Notes documenting the May 16, 2026 Screen Time passcode failures at approximately 12:20 PM.
  9. Notes documenting the May 16, 2026 Orbic device-count irregularity at approximately 1:03 PM.
  10. Notes documenting that I had not left Apartment Unit 2**.
  11. Notes documenting that I had not communicated with anyone using my Apple iPhone 17.
  12. Notes documenting that only my Apple iPhone 17 should have been connected to Verizon-RC400L-7E.

XVIII. Requested Apple Review

I request that Apple or a qualified Apple security reviewer evaluate the following:

  1. whether my Apple ID / iCloud account shows unknown trusted devices;
  2. whether my Apple ID shows unknown sessions, browser access, device access, or recent sign-in activity;
  3. whether any Screen Time passcode reset occurred on or around May 16, 2026;
  4. whether the Screen Time passcode could have been changed through the “Forgot Passcode?” process;
  5. whether my Apple ID email address and password were used in connection with Screen Time passcode reset;
  6. whether any unknown device had access to my Apple ID;
  7. whether any device-management profile, VPN profile, configuration profile, certificate, or unknown account was present on my Apple iPhone 17;
  8. whether iMessage access logs, Apple ID security notices, or trusted-device notices show irregular activity;
  9. whether an Apple Private Wi-Fi Address change could explain the Verizon Orbic RC400L displaying two connected devices;
  10. whether the device number associated with my Apple iPhone 17 shows any abnormal behavior;
  11. whether any device mirroring, cloning, unknown relay, or account-session issue is technically supported by the available evidence.

XIX. Requested Verizon Review

I request that Verizon review the following:

  1. whether any unknown IMEI, IMEI2, ICCID, EID, or eSIM profile was associated with my Verizon line;
  2. whether my Apple iPhone 17 device number shows signs of unauthorized access, transfer, reprovisioning, or device association;
  3. whether any SIM/eSIM download, transfer, reactivation, refresh, or reprovisioning occurred;
  4. whether any account-access event occurred on or around May 15 or May 16, 2026;
  5. whether any port-out, transfer PIN, account lock, customer-care, or in-store account event occurred;
  6. whether the Verizon Orbic RC400L can produce a connected-client list for approximately 1:03 PM on May 16, 2026;
  7. whether the Orbic connected-device indicator reflects active clients only or also stale/cached clients;
  8. whether Verizon-RC400L-7E had any unknown Wi-Fi client connected at approximately 1:03 PM;
  9. whether device-count data, DHCP leases, IP addresses, or administrative records can identify the second displayed device;
  10. whether Verizon can confirm that account takeover protection, number lock, port protection, SIM/eSIM protections, and account PIN protections are active.

XX. Requested Property-Management Review

I request that property management review the following:

  1. whether the woman observed on the Building 1 patio is associated with Apartment 3** or another unit;
  2. whether any prior complaints exist involving shouting, threats, harassment, or intimidation from that location;
  3. whether surveillance footage, Ring footage, hallway footage, or exterior footage exists for May 15, 2026, around 9:30 PM;
  4. whether surveillance footage, Ring footage, hallway footage, or exterior footage exists for May 16, 2026, from approximately 12:00 PM to 1:15 PM;
  5. whether any tenant was observed shouting from a patio door during the relevant time periods;
  6. whether any tenant made statements about my identity, backpack, Lands’ End tote bag, businesses, or personal devices;
  7. whether any lease, safety, nuisance, harassment, or conduct provisions apply to threats made from a patio area;
  8. whether written communication can be used going forward to protect my safety and avoid direct confrontation.

XXI. Recommended Follow-Up Evidence Steps

To strengthen the record, I should continue documenting this issue in a controlled manner:

  1. Preserve all screenshots in original form.
  2. Preserve the original date and time of each screenshot.
  3. Preserve the Apple iPhone 17 lockout screenshot as Exhibit A.
  4. Preserve the Screen Time reset-path screenshot as Exhibit B.
  5. Preserve the Verizon Orbic RC400L / Rayhunter two-device display as Exhibit C.
  6. Take a screenshot of the Orbic admin connected-client list, if available.
  7. Record each connected device name.
  8. Record each IP address.
  9. Record each MAC address or Apple Private Wi-Fi Address, if visible.
  10. Disconnect the Apple iPhone 17 from Verizon-RC400L-7E and check whether the count changes.
  11. Reconnect the Apple iPhone 17 and document whether the count becomes one or two.
  12. Reboot the Orbic and document the count before and after reboot.
  13. Change the Orbic Wi-Fi password and document whether the second count remains.
  14. Preserve any Rayhunter captures from the same time period.
  15. Preserve Verizon account notices, Apple ID security notices, OTP messages, and Amazon reminder text evidence.
  16. Communicate with property management in writing only.
  17. Avoid direct communication with the suspected speaker.
  18. If any further direct threats occur, document the date, time, words used, location, and any available witness or camera evidence.

XXII. Formal Incident Statement

I did not authorize any person to take, access, control, claim, search, interfere with, or possess my backpack, Lands’ End tote bag, personal devices, personal effects, identity documents, business documentation, Apple iPhone 17, Apple iCloud account, Verizon account, Verizon device number, Verizon Orbic RC400L, Verizon-RC400L-7E Wi-Fi network, or business projects.

I did not authorize any person to reset, change, interfere with, mirror, clone, duplicate, monitor, or control my Apple iPhone 17 Screen Time passcode.

I did not authorize any person to access my Apple iCloud account, Apple ID email address, Apple iCloud password, Verizon account, eSIM, or device number.

I did not invite or consent to the verbal statements made on May 15 and May 16, 2026. I do not know the woman as an acquaintance. I have not communicated with her. I do not live in Building 1. I did not respond to her statements, and I did not engage with her.

XXIII. Final Technical and Safety Conclusion

The May 15 and May 16, 2026 evidence supports a serious incident record requiring preservation and review.

The most accurate conclusion is:

On May 15, 2026, at approximately 9:30 PM, while I was writing JavaScript codes for VaultInbox.Cloud from inside Apartment Unit 2**, I heard an African American woman shouting statements involving my sex, identity, backpack, Lands’ End tote bag, refusal to communicate, and businesses I created. After the statements stopped, I observed an African American heavy-set woman standing on a Building 1 patio, most likely at Apartment 3**. On May 16, 2026, shortly after I successfully accessed iMessage to retrieve a bank OTP at approximately 12:16 PM, I heard the woman shout a direct threat to shoot me if I did not give up my identity, backpack, and Lands’ End tote bag. At approximately 12:20 PM, my Apple iPhone 17 Screen Time passcode 7457 failed repeatedly, even though I had updated it from 8515to 7457 the prior day and had just used it successfully. At approximately 1:03 PM, my Verizon Orbic RC400L Rayhunter device displayed two connected devices on Verizon-RC400L-7E when only my Apple iPhone 17 should have been connected. The evidence does not yet prove device cloning, mirroring, or unauthorized access, but it warrants review by Apple, Verizon, property management, law enforcement, or a qualified technical reviewer.

XXIV. Exhibit List

Exhibit A — Apple iPhone 17 Screen Time Passcode Lockout

Screenshot showing Apple iPhone 17 Screen Time passcode lockout for five minutes after repeated failed attempts using passcode 7457 on May 16, 2026.

Exhibit B — Screen Time Passcode Reset Path

Screenshot or documentation reference showing the Screen Time “Turn Off Passcode” screen and “Forgot Passcode?” option, preserved because I am concerned that an unauthorized person may have used or attempted to use the reset process.

Exhibit C — Verizon Orbic RC400L / Rayhunter Device Count

Photograph or screenshot showing the Verizon Orbic RC400L Rayhunter device displaying two connected devices on the Verizon-RC400L-7E Wi-Fi network at approximately 1:03 PM on May 16, 2026, when only one device was expected.

Exhibit D — May 15 and May 16 Timeline

Written timeline documenting:

  • Screen Time passcode updated from 8515 to 7457 on May 15, 2026, at approximately 5:10 PM;
  • first verbal incident on May 15, 2026, at approximately 9:30 PM;
  • bank OTP / iMessage access on May 16, 2026, at approximately 12:16 PM;
  • second verbal threat shortly after the 12:16 PM bank OTP access;
  • Screen Time passcode failure and lockout at approximately 12:20 PM;
  • Verizon Orbic RC400L / Rayhunter two-device display at approximately 1:03 PM.

XXV. Closing Statement

This report is prepared to preserve my observations, timeline, quoted statements, device-security concerns, Verizon Orbic RC400L / Rayhunter device-count irregularity, and the hostile housing impact of the incidents described.

The report is not presented as a final forensic determination. It is a written record for review because the incidents involved direct threats, identity-related statements, threatened taking of personal effects, suspected device-security interference, and an unexpected connected-device count on my Verizon Orbic RC400L Rayhunter device.

Respectfully submitted,

Sarai Hannah Ajai
*****, ***** ******
Date: May 16, 2026

 









Labels:
Location: Fargo, ND, USA

Comments

Post a Comment