Practical Security Awareness

You scanned a QR code. This one was safe.

A malicious QR code could have sent you to a fake login page, payment trap, or malware-related destination. Learn what to look for before the risky click.

Phone scanning a QR code with a safe check indicator

Start where you are

Example of a suspicious login page

I want to avoid scams

Learn common scam patterns and practical habits that reduce your risk every day.

Go to Scam Library
Example suspicious delivery text and payment prompt

I think I clicked something bad

Use the response checklists to decide what matters most and what to do first.

Go to What To Do Now
Secure coding checklist and code editor illustration

I build software, websites, or AI tools

Reduce unsafe defaults in auth, logs, file uploads, and automation workflows.

Go to Builder Guidance

Common traps

QR sticker scan risk example

QR scams

Hidden destinations that look harmless until after scan.

Fake login website warning example

Fake websites

Lookalike domains that steal credentials and MFA codes.

Delivery fee scam message example

Delivery scams

Urgent package messages that request tiny “fees.”

Fake fraud alert text example

Fake bank alerts

Impersonation messages that create panic and rushed approvals.

Impersonation call verification example

AI voice impersonation

Synthetic voices asking for immediate transfers.

Browser tech support scam popup example

Fake support scams

Scare screens and fake technicians requesting remote access.

Latest guides and updates

Developer / AI Track

Secure habits for builders

Security failures in modern products are often unsafe defaults, not advanced exploits. Start with auth checks, secret hygiene, bounded agent permissions, and explicit approval flows for risky actions.

Mission

Plaintext Security exists to make security advice practical and understandable. No fear tactics, no blame, and no enterprise buzzwords.

Read about the project