1. Write the observation plainly
Record the exact message, app or account involved and the time. An original example is “an unfamiliar sign-in alert appeared at 10:20,” rather than “AI took over my phone.” Do not add credentials or verification codes to the note.
If a screen can be recorded safely without exposing private information, keep it privately for support. This worksheet is not a forensic procedure; changing or deleting things can lose useful context.
2. Verify through a known path
Open the provider’s official support or account page through a known address, rather than a link or phone number supplied in a threatening message. NIST’s phishing guidance supports independent verification of suspicious requests.
For Android concerns, Google’s official guidance includes Play Protect, security updates and reviewing unsafe software. Follow the instructions that match the actual device and situation, or contact the manufacturer. This article does not diagnose the device.
Basis: NIST — Phishing guidance · Google — Remove malware or unsafe software
3. Preserve contact while deciding
Before changing radios or account access, consider how you will reach help and whether a trusted separate device is available. Do not isolate your only communication channel on the basis of an unverified rumour.
AI Rogue is an informational section inside Prepper. Supported Prepper requests can be paused deliberately, but that is not a phone-wide lock or malware scan. Record what you chose, why, and how to restore a trusted connection. Use official support for recovery rather than public-board instructions asking for secrets.
ORIGINAL WORKSHEET
Suspected incident card
Blank record. Keep screenshots and personal details private.
| Observation | Evidence / uncertainty | Known next action |
|---|---|---|
| Exact message + time | ________ | ________ |
| Affected app / account | ________ | Official path: ________ |
| Trusted contact method | ________ | ________ |
| Settings changed + restoration plan | ________ | ________ |
Save it. Then test it.
One reading file, 5.4 KB. No maps, external images, scripts or personal records. External source links still need internet.
Checks remain only during this visit. They do not certify readiness, safe equipment or successful delivery. The saved worksheet has blank prompts.
Save on this computer, or copy the completed download to a compatible USB drive. Reopen from that location for the offline test.
READ THE BASIS
Sources, dates and limits
Editorial incident organization, not qualified security assessment, malware detection or evidence that an AI attack occurred. Urgent personal safety needs take priority over an app checklist.
Source links checked 2026-10-11. The organization and sample worksheets are original editorial work. A source check is not a qualified review or a physical-device test. Downloaded files are dated snapshots; use current local guidance and equipment instructions.
- NIST — Phishing guidanceUnited States security awareness
- Google — Remove malware or unsafe softwareAndroid; manufacturer support may be needed
CONTINUE WHEN IT IS USEFUL
Use the matching Prepper task
This opens information; it does not automatically pause Prepper or change phone settings.
Open the Rogue AI incident reference →The installed product is Prepper. AI Rogue is a section inside it. An article or website release does not verify a public store listing, an update received by your phone, live LoRa messaging or an OS lock.