Lock Down Your Stuff
Scams and account takeovers are at record levels, and almost all of them work by tricking a person, not by breaking technology. The steps below take about two hours spread over a few evenings, cost little or nothing, and stop the large majority of attempts. Check the boxes as you go. Steps are numbered so you can tell a family member "do step 3.2." Total time: about 2 hours for a first pass. Sections 4 (credit freezes) and 7 (Wi-Fi) can wait for a weekend.
1. Do these five tonightabout 30 minutes
each one closes a door that thieves are using this month. If you only do one section, do this one.
2. Your emailabout 20 minutes
whoever controls your email can reset your bank, your phone account and everything else, so it gets the strongest protection you have.
3. Your phone and phone numberabout 25 minutes
the biggest phone risk is not a virus. It is someone talking your carrier into moving your number to their phone, then receiving your bank codes. Every major carrier has a free lock for this.
4. Bank and moneyabout 20 minutes, plus 15 minutes per credit bureau
the law protects you from charges you did not make if you report them fast, but money you were tricked into sending yourself is often gone for good. So the goals are to see problems the minute they happen and never hand anyone the keys.
5. Texts, calls and scamsabout 10 minutes to read, then habits
almost every scam has the same shape. Someone pretends to be a company or agency you know, claims a problem or a prize, pressures you to act right now, and insists on one payment method. Slow down and the scam falls apart.
6. App connections and account check-upsabout 20 minutes
over the years you have tapped "Sign in with Google" or "Allow access" dozens of times. Each one is a door that stays open until you close it.
7. Home Wi-Fiabout 20 minutes, one weekend
your router is the front door for every device in the house. Most of these settings are in your internet provider's app or the router's web page.
8. If something goes wrongread now, about 5 minutes
speed matters most. Reporting the same day gives you the best chance; waiting days usually means the money is gone.
9. Your paper kitabout 15 minutes
if your phone is lost or the internet is down, paper still works. Keep one sealed envelope in a safe place and tell one trusted person where it is. See the template below.
Family Recovery Sheet
One printed page, both sides if needed, large type. Fill it in by hand, seal it, and keep one copy at home and one with a trusted person.
- Date prepared / review by (Today's date and one year from now)
- Bank 1, Bank 2, Credit union (Name, fraud phone number (from back of card), last 4 digits of the account only, what the account is for) Never write: Full account number, PIN, online password
- Credit cards (Issuer, fraud number, last 4 digits) Never write: Full card number, expiration, security code
- Phone carrier (Carrier name, customer service and fraud number, account holder name, "Account PIN is kept: ___ (location, e.g. sealed inner envelope)") Never write: The carrier PIN in the open
- Credit bureaus (Equifax 888-298-0045, Experian 888-397-3742, TransUnion 800-916-8800, plus "logins are in: ___ (password manager name)") Never write: Bureau passwords
- Email provider(s) (Which email is the "master" email; recovery page address (accounts.google.com/signin/recovery, iforgot.apple.com, account.live.com/acsr)) Never write: The email password
- Backup codes ("Google backup codes are in: ___ (location)" or tape the printed codes inside the sealed inner envelope) Never write: Codes written on the outside of anything
- Password manager (Which one, and where the emergency kit or recovery code is stored) Never write: The master password
- Reporting (ic3.gov, ReportFraud.ftc.gov, IdentityTheft.gov, local police non-emergency number)
- Family contacts (Name, cell, a second number, and one out-of-town contact who relays messages if local lines are down)
- Family code word (The word, plus the rule: "no money moves without the code word, even if the voice sounds right")
- Meeting place (Primary (near home) and secondary (outside the neighborhood))
- Trusted person (Who knows where this envelope is, and who holds the second copy)
- Medical (Doctor and pharmacy numbers, allergies, prescription names and doses, insurance member numbers (these can go in the inner envelope))
- Accounts to notify (Short list of accounts tied to the master email (bank, carrier, cloud photos, social) so nothing is forgotten after a takeover)
- Devices (Phone make and model, carrier, and where the Find My or Find Hub login lives)
- Put the sheet in a sealed envelope and sign across the seal. Keep one at home in a place a visitor would not find (not the kitchen drawer) and a second copy with the trusted person or in a safe deposit box.
- Anything secret (carrier PIN, backup codes, insurance numbers) goes in a smaller sealed inner envelope inside the main one, so the outer page can be used without exposing them.
- Never write full passwords, full card or account numbers, Social Security numbers, or the password manager master password on paper. Write where they live instead.
- Do not photograph the sheet with your phone; a copy in your photo library defeats the purpose.
- Replace the sheet when you change a phone, carrier, bank or email. Shred the old one.
Tools to check yourself
Tools people are using to check and protect themselves, grouped by who they are for. Status says how far each one has been checked: Verified means read on the maker's own docs or repo; Seen on X means recommended by credible accounts but not yet read; Community means popular but unaudited, so only in a throwaway VM and never in a session that can reach your bank, email or wallet.
Developers and anyone who runs a website11
A coding-agent skill that runs a multi-phase security audit (recon, hunting, independent validation, report) on any codebase, model independent; about 34,000 GitHub stars on Oct 21. Heavy token use.
npx skills add https://github.com/cloudflare/security-audit-skill --skill security-auditChecks whether a PHP site or server is exposed to PHP2Shell (CVE-2026-109618 and CVE-2026-109619). Run it against every PHP site you own or host, then upgrade PHP.
Free on all plans. Runs while Claude writes code: pattern check on every edit, background review at the end of each turn, deeper review on commits. Per-repo rules in .claude/claude-security-guidance.md.
/plugin install security-guidance@claude-plugins-officialOne pass over the current branch's changes. Quick, but it does not scan the whole repository.
/security-reviewMulti-agent scan of a whole repo, a branch, a PR or a commit; every finding is checked by independent verifier agents; writes Markdown, JSONL and SARIF reports and can draft patches you apply with git apply.
/plugin install claude-security@claude-plugins-officialLists known vulnerable dependencies in a PHP or JavaScript project. Run before and after every update.
composer audit | npm auditFinds secrets (API keys, tokens, passwords) anywhere in a repository's history, which is how leaked keys usually get found by attackers first.
gitleaks detect --source .Static analysis rules for common vulnerability classes plus a secrets scanner; free for local use.
semgrep scan --config autoGrade a public site's certificate, TLS setup and security headers from the outside in under a minute. Useful after the eMudhra certificate revocations.
The security and performance advisors flag missing row-level security and exposed tables per project; the agent skills teach coding agents the safe patterns.
npx skills add supabase/agent-skillsFree alerts for leaked secrets and vulnerable dependencies; turn both on in each repo's Security tab.
Everyone9
One page that lists weak spots on your Google account: recovery info, devices, third-party access, reused or leaked passwords.
The strongest Google account setting: security keys or passkeys only, blocks most third-party app access. Meant for people who are targets, which includes anyone with a large following or crypto.
Shows which breaches included your email or phone number. Set up notifications so new breaches reach you.
A different password for every account is the single biggest reduction in account takeover risk. Never connect a password manager to an AI agent.
A physical key that cannot be phished. Buy two directly from yubico.com, add both to email, bank, exchange and GitHub.
Free, stops new credit in your name. Each bureau separately; children can be frozen by mail.
SIM Protection and Port Out Protection (T-Mobile), Number Lock (Verizon), Wireless Account Lock (AT&T). Stops the SIM swap that steals your text codes. Exact menu paths are in the checklist, section 3.
iPhone Stolen Device Protection; Android Theft Detection Lock, Offline Device Lock and Remote Lock; Android 16 Advanced Protection and Apple Lockdown Mode for higher-risk people.
Microsoft Defender Offline scan catches what a running system hides; Sysinternals Autoruns shows everything that starts with Windows, the best way to spot something that should not be there.
Crypto holders4
Genuine Check confirms the device firmware is Ledger's; it did not catch the CryptoBilis hardware implants, so buy only from ledger.com and move funds to a new seed on a new device if yours came from a reseller.
Chain state > proxy > proxies(your coldkey) lists every proxy on a Bittensor or Polkadot account, so a forgotten staking proxy can be removed.
Emergency responders for crypto drains and compromises; the first call if funds are moving.
Delay changes to security settings by a week or more, restrict withdrawals to your own addresses, and audit API keys.
Community AI security tools, popular on X, not audited4
Lets an agent drive 150+ offensive tools (nmap, sqlmap, nuclei). Authorized targets only, isolated VM only.
A huge kit of skills; if used, take only its security-review skill after reading the source.
83 vulnerability-audit skills. Read before installing; hooks run code on your machine.
/appsec:secrets, /appsec:dependency-check and an OWASP checklist skill for Claude Code.
- Official first (the maker's own tool), community last and only after reading the source.
- Never install a community skill, plugin or MCP server in a session that also has bank, email, exchange or wallet access.
- Scan only sites and repos you own or are authorized to test.
- Pin versions and recheck after updates; a tool can be fine today and trojaned tomorrow (LiteLLM 1.107.0 was).
Other places to watch
free, no sign-up- CISA Known Exploited VulnerabilitiesExploited right now: The US government list of flaws attackers are using today, with patch deadlines.
- CVE TrackerVulnerability counts and data: Published CVEs per month since 1999, daily and cumulative, rebuilt every day from the official list.
- Have I Been PwnedBreaches and your accounts: Check whether your email address is in a known breach.
- Cloudflare RadarInternet health and outages: Live internet traffic, outages and attack trends by country.
- CISA alerts and advisoriesGovernment and CERT alerts: US alerts, joint advisories and emergency directives.
- BleepingComputerNews worth following: Fast, hands-on coverage of attacks and fixes.
Updated Nov 5, 01:42 UTC. Refreshes on its own.