BlurThis

Home/Blog/

Don’t screenshot the WhatsApp code

Hijackers ask contacts to read a six-digit SMS. A screenshot of that code is the whole attack.

A phone lock screen held in a hand
Photo from Unsplash

The scam is not “unblurred chat.” The scam is a code.

Reporting on WhatsApp hijacks — including crime coverage in 2026 — keeps describing the same beats: someone wants your number moved, or they want the SMS that WhatsApp sent, or they talk a relative into reading the six digits aloud. A screenshot of that SMS is a gift. Delete it. Do not post it to “prove” the message looked official.

Sowetan’s 3 August 2026 piece on WhatsApp scammers and money theft sits in that coverage: number, code, SIM-swap style takeover. This post does not invent a named victim whose only mistake was a light blur. Posting a still that still shows a number or an OTP feeds the same crime those articles describe.

What can a screenshot still feed?

If the thread shows the phone number and a preview of the SMS, you handed over two ingredients. Cover the number even when you are only showing a sticker. Cover the code always. Delete the code from the camera roll. Do not forward the SMS as an image into a family group “so they can see it was real.” Real is a sentence in your own words. The digits are the payload.

SIM-swap chain: SIM-swap chain. Chat hygiene when the shot is not an OTP: WhatsApp screenshots.

Why would anyone screenshot an OTP on purpose?

Support asks for “what you saw.” Relatives ask “is this legit?” People post the banner to a forum. All of those requests can be answered without the digits and without the full number. Describe the sender name. Describe that it said WhatsApp. Do not photograph the six characters. Do not photograph the header that prints +country and the rest.

If you already captured it, bar both, export PNG, then delete the original. Do not keep a “for my records” copy of a live login code. Codes expire. Screenshots do not.

Is blur enough on a six-digit code?

Six digits are the short-alphabet case. A polite smear can leave stems. A highlighter tint can be stretched. This is not a claim that a named person was hijacked because of Gaussian blur. It is the narrower rule: do not leave the code in the file. A solid bar, or better, no photograph of the code at all.

Does the number in the header matter if the code is gone?

Yes. Takeover reporting describes needing the number and the OTP. The number is how a port-out or a social-engineering call starts. A sticker screenshot with a clean header is a number you published. Cover the header. Crop if you do not need it. Recapture after you hide the number in WhatsApp settings if you are posting a chat for another reason.

What should you do if someone asks you to send the SMS screenshot?

Refuse the digits. If they are support, use the in-app path, not a PNG of a one-time code. If they are a relative, read nothing aloud that is a code. If they are a stranger, stop. The Sowetan coverage is about theft, not about forum etiquette. A screenshot is a way the ingredients travel farther than the call.

Notification shade shots of the same SMS are the same SMS. Lock-screen photos of the same SMS are the same SMS. A cropped banner that still shows six digits is still the code. Delete Recents copies after you refuse. Cloud photo backup will otherwise keep the factor for months. Relatives who mean well will still ask for the picture. Answer with the sender name only. Do not negotiate the digits “just this once.” Do not screenshot the WhatsApp “linked devices” screen either if it shows the number you are trying to protect.

No named victim in this post whose “only mistake was blur.” The honest line is narrower: do not photograph the code, and do not leave the number in the header. The ingredients are the crime. bar the header and delete the code.