The cafe Wi-Fi that listens
The I4C's warning on eavesdropping attacks: on an open network, whatever travels unencrypted can be read, copied or changed in transit - and a lock icon means the connection to that site is encrypted, not that the site is honest. How the listening works, what actually protects you, and the habits worth keeping.
The airport lounge, the cafe, the hotel lobby: the Wi-Fi is free, the password is on a chalkboard, and within a minute you are reading email and checking your balance. India's cyber-crime coordination centre, the I4C, has a name for what can happen on that connection - its advisories listing of 22 April 2022 warns of eavesdropping attacks, in which criminals intercept, delete or modify network traffic as it travels. On a network you do not control, the line between your phone and the internet runs through equipment you cannot see and people you cannot name.
How the listening works
CISA, the US cyber-security agency, describes the simplest version: many public access points are not secured, and the traffic they carry is not encrypted - transmitted "in the clear", where sniffing tools can pick out passwords and card numbers. A password on the network does not settle it: the NSA's guidance on public wireless notes that even where a public network does encrypt traffic, anyone who knows the shared key - everyone the chalkboard told - may be able to decrypt what others on it send. Then there is the lookalike. In what CISA calls an evil twin attack, someone gathers the details of the real hotspot, then broadcasts a stronger signal under the same name; join the stronger one, and everything you send passes through the attacker's system first. None of this needs you to do anything unusual. That is the point of the I4C's warning: the listening is silent, and the network feels normal.
What the lock icon does and does not say
Most of what you do now travels over HTTPS - the encrypted form of the web - and Mozilla's explanation of its HTTPS-Only Mode puts the difference plainly: plain HTTP is cleartext that attackers on the network can view, steal or tamper with, while HTTPS creates an encrypted connection between your browser and the website. Chrome's own help page is careful with the meaning: a site using HTTPS "can indicate a secure connection". Read that carefully. The lock says the connection to that exact address is encrypted, so the cafe's network cannot read the contents. It does not say the site at the other end is honest - a fake shop can have a perfectly valid lock, the way signed malware can carry a perfectly valid signature. And the protection only holds if you do not click past the browser's certificate warning: that warning is the browser telling you it cannot validate the certificate on this connection - a name that does not match the address is one possible cause, not the only one.
What actually protects you
The strongest move costs nothing: do sensitive things on a network you control. The NSA's first advice is to avoid public Wi-Fi when possible and use your own mobile data or a personal hotspot instead, which is exactly backwards from the habit of saving data by joining free Wi-Fi for banking. If you do join, confirm the hotspot's exact name with the staff before connecting - CISA's advice against the evil twin - and say no when the device asks about sharing files, printers or AirDrop with the network. Keep the browser's guard up: in Chrome, the "Always use secure connections" setting upgrades sites to HTTPS and warns before one that cannot; in Firefox, HTTPS-Only Mode attempts a secure connection to every site and asks before connecting to one that does not support it. And never click past a certificate warning on a network you do not control. On public Wi-Fi, the NSA strongly advises a personal or corporate VPN, which encrypts your traffic as far as the VPN provider - understand it as moving trust to a provider you chose, not as a force field, and pick the provider with that in mind. The NSA is plain that no set of practices fully protects; these are the measures that cut the documented risks.
If you think you were listened to
There is rarely a siren: the listening leaves no pop-up. Act on the possibility, not on proof. From a network you trust - your mobile data, your home Wi-Fi - change the passwords of the accounts you used on the suspect network, email first, and turn on multi-factor authentication where it is offered; the NSA lists MFA among the practices that blunt stolen credentials. Watch your bank and card statements for a while. If money moved, call 1930 - the national financial-fraud helpline - immediately and inform your bank; if you typed card or banking details anywhere that now looks wrong, tell the bank that directly. Report the incident itself at cybercrime.gov.in. None of this rewinds what was sent; it closes the doors the stolen keys still fit.
The shape worth remembering
A network you do not control is a room you cannot see. The chalkboard password makes the room shared, not safe, and the lock icon guards the pipe, not the people at its ends. So do the sensitive things on your own data, join only the hotspot you confirmed, keep the browser's HTTPS guard up, and treat a certificate warning as the wall it is. The listener's advantage is silence; the answer is a short list of quiet habits that cut the documented risks, kept without being asked.
Sources: the national cybercrime portal's advisories page - official listing of the I4C advisory "Cybercriminals perpetrating Eavesdropping attack to steal sensitive data" (22 April 2022); the NSA's information sheet on securing wireless devices in public settings (July 2021) - shared-key decryption, the advice to avoid public Wi-Fi or use a personal hotspot, the VPN recommendation, and the caveat that no practices fully protect; CISA's guide to securing wireless networks - cleartext sniffing, the evil twin attack, and confirming the hotspot before joining; Chrome's safety settings - "Always use secure connections" and the "Not Secure" warning; the Mozilla Security Blog - HTTPS-Only Mode and why plain HTTP is cleartext. Fraud reporting: 1930 and cybercrime.gov.in.
Frequently asked questions
The Wi-Fi had a password. Doesn't that make it safe?
Not from the others on it. The NSA's guidance is specific: even where a public network encrypts traffic, anyone who knows the shared key - and a cafe's chalkboard gives it to everyone - may be able to decrypt what other users send. The password keeps out people who are not on the network; it does not hide you from the people who are. HTTPS still protects the contents of each secure connection, which is why the browser guard matters, but the network password itself is not your privacy.
Does the lock icon mean the site is genuine?
No. The lock means the connection between your browser and that exact address is encrypted - Chrome's own wording is that HTTPS "can indicate a secure connection". It says nothing about who runs the site: a fake shop or a lookalike login page can have a valid lock, just as signed malware can carry a valid signature. The check that matters is the address itself, reached by a route you chose - your own bookmark or the official app - plus never clicking past a certificate warning.
Is a VPN a complete answer on public Wi-Fi?
No, though it is a real layer. The NSA strongly advises a personal or corporate VPN on public Wi-Fi because it encrypts your traffic as far as the VPN provider, blunting local eavesdropping and the evil twin. What it cannot do is vouch for the sites you visit or make a dishonest provider honest: you are moving trust from the cafe's network to the VPN company, so choose it with the same care. The NSA itself cautions that no set of practices fully protects.