The story is an anecdote, and it is the tester's own account. The client isn't named. Nothing independent confirms the details, and there's no date for when the test took place. Read it as a well-told cautionary tale, not a forensic report.
What happened, according to the tester
Christian Espinosa is a certified penetration tester and the CEO of Blue Goat Cyber. He told The Register that he starts an engagement by walking the physical space, because real attackers do the same. That detail comes from his quote in the story, not from the search results.
On one client walkthrough he spotted a password written on a sticky note taped to an employee's monitor. By his account, the sequence went like this:
- He photographed the note.
- He used the password to sign in to that employee's account, and it worked.
- He tried the same password on the company VPN, which the employee reportedly maintained. It worked there too.
- Once on the VPN, he says he had broad network access, including every shared drive that account could reach.
The data he says he found was extensive:
- HR folder: employee home addresses, driver's licenses, scanned W-4 forms and salary spreadsheets.
- Server inventory: a document listing internal server names and the people responsible for each. The Register notes this is useful for phishing.
- Accounting server instructions: a document explaining how to log in to the accounting server.
- Accounting server contents: vendor banking details, invoices and payment records.
Espinosa framed the exposure as enough to enable payroll fraud, identity theft or vendor-payment fraud. The story does not say any of that actually happened.
How the client responded
After the tester presented his findings, the client reportedly did four things:
- Disabled the account.
- Started reviewing VPN access logs to see whether anyone else had gotten in.
- Searched the office for other exposed passwords.
- Tightened permissions on the HR and accounting shares so only people with a real need could reach them.
The story doesn't say what the log review found. It doesn't say whether the VPN required MFA, whether the password was reused elsewhere, or whether credentials were rotated or affected staff were notified. I won't guess at any of those.
Espinosa's sharpest point is that the risk outlived his visit. In his words, someone could have photographed the note, left, and connected to the VPN that night from anywhere.
It isn't really a sticky-note problem
The sticky note was only the first failure. The chain needed several things to line up, and breaking any one of them would have changed the outcome:
- A visible credential. Anyone in the office could see it.
- A password that worked for remote access. Reportedly it was the only thing standing between a visitor and the VPN.
- An account with too much reach. A single employee login led to sensitive HR data, a server map and accounting instructions.
- Possibly thin detection. The story doesn't say whether anyone would have noticed an odd late-night VPN login.
Reasonable people can disagree on how much blame the employee deserves. The policy and architecture failures arguably matter more. If one user's password can expose payroll data and vendor banking details, the real fault is in how the shares were set up, not in the sticky note.
What government guidance says about each link
The mitigations are not exotic. They appear again and again in US government guidance. These are general recommendations, not findings about this client.
MFA on VPN connections. The joint StopRansomware Guide advises organizations to implement MFA on all VPN connections. It also lists compromised credentials as an initial access vector and urges phishing-resistant MFA for all services, particularly email, VPNs, and accounts that access critical systems. With MFA, a password read off a note isn't enough on its own. The same guide offers a weaker fallback for when MFA isn't in place: passwords of 15 or more characters. Length wouldn't have helped here, because a password on a sticky note is exposed however long it is.
Least privilege. The same guide says to apply least privilege to all systems and services so users only have the access they need to perform their jobs. CISA's joint guidance on modern network access makes the point for remote users specifically: users should only have access as it pertains to their role within the organization. A VPN login shouldn't mean "the whole file server."
Zero trust access policies. The StopRansomware Guide also recommends strong access policies that restrict user-to-resource access and resource-to-resource access. In practice, a general employee account shouldn't be able to walk from a shared folder to an accounting server.
Layering. MFA doesn't fix everything. One roundup of CISA guidance notes that CISA has documented both VPN exploitation and an MFA bypass caused by a software vulnerability. That is why the controls need to work together instead of any one of them being treated as enough.
A checklist for IT teams
If you find a password in plain view, this is a sensible response. It's my synthesis of the story and the guidance above, not a formal procedure.
- Treat the credential as compromised. Remove the note and change or invalidate the password through your incident process.
- Find everywhere it was used. The story says one password worked on both a user account and the VPN. Resetting one login doesn't help if the secret was reused.
- Check the logs. Preserve and examine sign-in and VPN records for unusual activity, especially off-hours remote access. Work out whether the account touched sensitive files.
- Audit file-share permissions. Start with HR, payroll and accounting. Remove broad group access and confirm that every person who can read a share needs to.
- Require MFA on remote access. Use phishing-resistant methods where your VPN and identity provider support them.
- Review operational documents. Server inventories and login instructions help legitimate admins, but they also help an intruder. Store them where only the right roles can read them.
- Sweep the office. Walk it as an attacker would, as Espinosa did. Check monitors, desk drawers, keyboards and whiteboards.
- Give people a better option. Staff who write passwords down usually do it because remembering many unique passwords is hard. NIST's current digital identity guidelines (SP 800-63B-4, finalized in July 2025) supersede the 2020 edition. Using a password manager to keep distinct passwords per service is a long-standing, widely recommended practice. The story says nothing about this employee's habits, so treat that as general advice, not a diagnosis.
The bottom line
The Register's PWNED column has a recurring theme. It's rarely a clever exploit. It's usually an ordinary shortcut that meets a permissive environment. This story fits that pattern. A note on a monitor became a VPN login, then an HR folder, then a path to the accounting server.
The fix is a stack of ordinary controls: MFA on remote access, tight permissions on sensitive shares, and monitoring that notices unusual logins. You also need a culture where nobody tapes the keys to the front door.
References
- Sticky note on monitor provided keys to the company’s kingdom The Register · 2026-11-19T10:15:00+00:00
- Modern Approaches to Network Access Security cisa.gov
- SP 800-63B-4, Digital Identity Guidelines: Authentication and Authenticator Management | CSRC csrc.nist.gov