November 2026: Hacklore turns one
November 2026: Hacklore turns 1! π

Intro
Next week, on November 24, it will be one year since a group of CISOs and security experts published an open letter asking everyone to stop repeating outdated security advice. Avoid public Wi-Fi! Never scan QR codes! Beware of juice jacking! Change your passwords every 90 days! We called it hacklore, and we asked people to spend their limited attention on the basics that actually stop real attacks.
We also call this kind of outdated advice zombie advice: it should have died years ago, but it keeps coming back. π§
So, dear hacklore.org reader, how did year one go? Honestly: better than I expected in some places, and worse than I hoped in others. Some of the biggest names in security awareness now say what we said. A national cyber agency told the public that passkeys should be their first choice. The College Board rewrote the public Wi-Fi section of its new AP course. And state governments? We'll get to them. Bring a snack. π¬
Back in August I promised a Cybersecurity Awareness Month roundup, worst offenders included. Buckle up! π
Zombie advice π§
Zombie of the Month! π₯
This month's winner isn't one page. It's three.
On October 1, the governors of Michigan and Alaska each signed a Cybersecurity Awareness Month proclamation urging residents to protect themselves by "creating unique passwords and changing them regularly." Same words, same order. North Carolina's governor went with a remix: "creating strong and unique passwords and changing them periodically."
I'm no Columbo, but I doubt three governors' offices each decided, on the same day and in nearly the same words, to bring back scheduled password changes. This sort of thing happens when organizations reuse a template that gets dusted off every October, signed, and posted. If that's what happened here, the zombie isn't in Lansing or Juneau or Raleigh. It's wherever that template lives.
Bonus irony: the same week, Michigan's own insurance department told residents to use 12 characters, no reuse, and a password manager. Same state. Same month. Opposite advice.
If you know where this wording comes from, please reply and tell me. If it is a template, fixing one document could fix dozens of proclamations next October.
π Breaking news! Here's a late-breaking entry! The Australian government posted this classic hacklore about public wi-fi. It's so cute that it must be true! π΅βπ«
Runners-up π₯
β‘οΈ Oklahoma's state IT office published a "31 Days of Cybersecurity" checklist. Day 27: "Update all account passwords." All of them. On one day. For no reason. I'm sure the help desk loved day 28. (Itβs an older post but still lingering.)
β‘οΈ The Illinois governor's office and its IT department told residents to "consider making them complex (upper, lowercase, numbers, symbols)." NIST dropped composition rules years ago. Length and uniqueness are what matter.
β‘οΈ The CISO of ARIN, the organization that hands out IP addresses for North America, wrote a Cybersecurity Awareness Month post recommending scheduled password changes: "A periodic refresh clears most of them out." It does not. A password manager does.
Treats π¬
In August I said the alternative to a trick is a treat. Plenty of organizations delivered.
β‘οΈ KnowBe4, the largest security awareness training company, published a Cybersecurity Awareness Month post by Anna Collard that reads like it came from our FAQ. "Forced 90-day rotation is the clearest example" of a policy that backfires, and "Length and uniqueness beat character requirements." Password managers, passkeys, the works. No mention of hacklore.org. Bravo!
β‘οΈ The National Cybersecurity Alliance built its 2026 campaign around four behaviors: a strong password with a password manager, MFA, spotting and reporting scams, and updating software. No myths. Its passwords page now says "you don't need to change them regularly," and its public Wi-Fi page says "many older warnings are outdated or exaggerated." Progress!
β‘οΈ CISA's 2026 toolkit sticks to strong passwords, MFA, and prompt updates. It says nothing about public Wi-Fi, QR codes, USB charging, or password rotation. Silence isn't a retraction, but it's a lot better than a skull on a QR code. Fab!
β‘οΈ Wisconsin gets the most improved award. π Governor Evers's 2025 proclamation urged "creating and regularly changing unique passwords." The 2026 version says "creating strong passwords, protecting their accounts with multi-factor authentication, keeping software updated." Proof that proclamations can be fixed. Yes!
β‘οΈ The governors of New York, Nevada, and South Dakota all signed proclamations with good advice. Nevada's recommends "long, unique passphrases (or a password manager)." MassCyberCenter recommended passkeys. Google used the month to push passkeys too. Glorious!
Year one: what changed π
The big wins π
β‘οΈ College Board rewrote the public Wi-Fi topic in AP Cybersecurity. This one makes me especially happy. The first version of the course framework, from 2025, had a topic called "The Dangers of Public Wi-Fi" that told students to "avoid joining unprotected wireless networks." The current Course and Exam Description renames it "Best Practices for Public Networks." The "avoid" line is gone. It now explains that most internet traffic is encrypted, and it adds that an attacker running a fake hotspot "cannot read traffic that uses an encrypted protocol like HTTPS." It even notes that your VPN provider can see your traffic. π This matters. The students taking this course are the next generation, and we owe them the best information we have. The first exam is in May 2027. Many thanks to the AP Cybersecurity team at the College Board who worked to make this update!
β‘οΈ The UK's NCSC said passkeys should be "consumers' first choice of login." In its April paper, the NCSC also said passkeys mean people no longer need to create complex passwords. That's a national agency telling the public what we've been saying.
β‘οΈ Passkeys went mainstream. The FIDO Alliance's Passkey Index says 36% of completed sign-ins now use a passkey, up from 26%. Passkey sign-ins succeed 93% of the time, compared with 78% for MFA. And Microsoft made passkeys the default sign-in method in Entra ID on September 1. That's a secure default doing what no awareness poster ever could.
Areas for improvement: state governments π
Over the past two months we read the public security advice from all 50 state governments. In 46 states we found at least one page telling everyday people to follow one of the myths in the letter: avoid public Wi-Fi, change passwords on a schedule, use complexity rules, and so on. In total we found 134 clear examples.
Details here: https://www.hacklore.org/states
If you work for a state government, it's time to update your advice to the public.
Hacklore to watch π
New myths are always forming. Here are a few spreading this year. None has a documented pattern of real attacks on everyday people.
β‘οΈ "Don't say yes on silent calls." The claim is that scammers record your voice to clone it with AI. Warnings spread in France and Malaysia. The Malaysian police admit they have no confirmed reports. Itβs never happened, but beware anyway! π«
β‘οΈ "Ghost tapping." TV stations warned that crooks are skimming contactless cards and phone wallets. The scary growth figure traces back to one expert's quote. π»
β‘οΈ Malicious charging cables. Lab tools that do this are real. Documented attacks on consumers are not.
β‘οΈ Turn off your home router before you travel. Australia is at it again! ASD made this recommendation (we covered that in February), and now Germany's BSI says it too. I've yet to hear the threat model.
Community update
Subscribers π
We have 787 subscribers! In August I asked you to help us reach 1,000 by the end of the year. We're 213 away with six weeks to go. If this newsletter helped you, forward it to two friends and we'll get there.
New hacklore.org π
The website got a makeover. We moved off our old hosting provider and launched a redesign built around the myths and the basics:
β‘οΈ A page for each of the seven myths: why it's outdated, what to do instead, sources, and common questions.
β‘οΈ A Basics page with the letter's recommendations.
β‘οΈ A Toolkit page with the poster, the slide deck, a QR code (yes, really), and t-shirts.
β‘οΈ An FAQ where every question has its own link, so you can send exactly the right answer to that one relative.
β‘οΈ The letter itself, unchanged.
It's also much faster. The home page illustration went from 2.6 MB to about 100 KB.
In the news π°
Some coverage from this year I haven't mentioned yet:
β‘οΈ Huntress: "Why It's Time to Kill the Hacklore."
β‘οΈ Lora Vaughn: "It's 2026. You Can Use the Guest WiFi." The title says it all.
β‘οΈ From Norway, netsecurity.no: "Hacklore: The Modern Folklore of Cybersecurity."
β‘οΈ And a look back at launch week: Business of Tech, GIGAZINE, and Nikkei xTECH. Hacklore went international in its first week. π
Misc.
β‘οΈ Traveling for Thanksgiving? Charge your phone wherever you like. Engadget looked into airport USB ports this month and found the threat is overblown, and ESET found no documented real-world case of juice jacking. Spend the energy on something that matters: turn on passkeys for your email, and help a relative set up a password manager while you're there.
β‘οΈ Follow the Hacklore Bluesky account, and tag us when you see hacklore in the wild.
Closing thoughts π
A year ago, some of us wondered if anyone would care about a letter asking people to stop worrying about airport Wi-Fi. You did. You sent zombies, forwarded newsletters, printed posters, and argued with your IT departments. Thank you.
Year two has an obvious to-do list: find out where that proclamation wording comes from, help the states clean up their pages, and keep pushing software manufacturers to ship secure defaults so nobody has to memorize a list of tips at all.
Happy Thanksgiving to those who celebrate. See you next time! In the meantime, keep fighting hacklore!
-Bob