Calendar invites bypass email filters and can auto-add without acceptance. See how the attack works and the settings that close most of the gap.
Calendar invite phishing uses a meeting invite to deliver an attack, not an email. The file format behind most invites is .ics. It often passes through email gateways without the same checks a message body gets. Worse, many calendar apps add invites on their own. So the attack can land in someone’s schedule before they decide anything. Stopping it means changing calendar settings, not just training people to spot bad emails.
The industry spent two decades hardening the inbox. Meanwhile, the calendar sat beside it, largely untouched.
That gap exists for a reason. A meeting alert does not feel like a message from a stranger. It feels like a system notice from a tool you already trust, such as your calendar or a video meeting app. People learn to treat those alerts as plumbing, not as new mail.
Attackers use that habit directly, the same way a remote access trojan relies on someone installing it willingly. An invite also carries more urgency than an email, since it implies a booked commitment with a time attached.
The mechanics differ from email phishing in ways that change the defense.
| Stage | What happens | Why it works |
|---|---|---|
| Delivery | Invite arrives as an .ics attachment | Many gateways do not inspect the file deeply |
| Auto-add | Calendar adds the event automatically | No click required for it to appear |
| Trust | Entry looks like a normal meeting | Platform branding carries built-in credibility |
| Payload | Invite body holds a link or phone number | The lure sits outside the email body |
| Persistence | The entry stays in the schedule | Reminders resurface it repeatedly |
The auto-add behavior is the part most people miss. Google Calendar offers three options for how invites get added: from everyone, only from known senders, or only after you respond in email. Under the broadest option, invites land on arrival whether or not the user accepts. An employee who never opened an email can still find a bad meeting sitting in tomorrow’s schedule.
Then reminders do the attacker’s work for free. A notice pops up at the set time, often when the person is busy and least likely to check it.
Discover how Threatcop protects your workforce from modern cyber threats.
A calendar entry can carry several kinds of lure. Some dodge link scanning entirely.
For example, a link in the invite body leads to a credential harvesting page. It usually copies a login screen for a familiar service. Meanwhile, a phone number in the location field turns the invite into a vishing setup, where the target calls the attacker rather than the reverse. Instructions to install a remote support tool can hand over device access, which is the same pattern behind many remote access trojan incidents.
But notice what the phone number version avoids. No bad URL for a scanner to flag. No attachment to open. The attack is a number and a story.
So default settings matter more here than training, because the attack can land with no user action at all.
So check the default on your own tenant first. The setting name differs by platform, and the safe option is often not the default. Google expanded admin controls in August 2026, so administrators can now set this for existing users rather than only new ones. That admin control still defaults to “From everyone,” and the Workspace admin guide lists all three options.
Calendar attacks leave traces, but not in the places most teams monitor.
Start with the mail flow, since email filters miss plenty already. Invites arrive as email first, so .ics attachments from outside domains show up in gateway logs even when the file itself passed inspection. A sudden volume of them from one sender, or invites addressed to many staff at once, is worth flagging.
Then check the calendar service logs. Most platforms record event creation, including who created an entry and whether it came from outside the organization. An outside account creating entries across many employees’ calendars is a campaign, not a scheduling mistake. Pull that list before deciding how far it spread.
Finally, watch for the follow-through rather than the invite. A spike in outbound calls to one unfamiliar number often surfaces faster than the invite that caused it. The same goes for a burst of remote support tool installs across unrelated teams.
So staff need a short, specific rule rather than general caution.
Treat an unexpected invite like an unexpected email. So do not call a number from inside an invite. Do not install anything a meeting asks you to install. If an invite claims to come from a colleague or vendor, confirm through a channel you already use. And report anything odd, even if it already appeared on your calendar, because arrival is not acceptance.
Still, one habit transfers from email training: check through a second channel. What does not transfer is the idea that an attack arrives as a message you have to open.
A program that only simulates email will never show whether staff fall for a calendar lure. The two trigger different instincts.
Threatcop Security Awareness Training (TSAT) runs simulations across several attack types. So the test reflects how attackers actually reach people, not just the inbox. Its Employee Vulnerability Score splits those who acted from those who only saw the lure. That split matters when an invite can auto-add with no decision at all. Average breach time, meaning how long from lure to a harmful action, shows the window an attacker would have.
Still, reporting closes what detection misses. A fast reporting route gives staff somewhere to send a suspicious invite, and reporter insight shows which other calendars received the same entry, turning one report into the scope of the campaign.
Calendar invite phishing works because the calendar kept the trust the inbox lost years ago. The fix is mostly configuration. Turn off auto-add. Restrict external invites. Make sure .ics files get inspected like any other attachment. Then teach one rule that holds on any channel: never call a number or install software because a notification told you to. That rule survives whatever the next delivery method turns out to be. Companies that hardened email but never opened their calendar settings have left a door propped open beside a reinforced one.
Calendar invite phishing delivers an attack through a meeting invite, not an email. The invite carries a bad link, a phone number for a vishing callback, or instructions to install remote access software. It often reaches the calendar without the recipient accepting it.
Because invites arrive as .ics attachments, many gateways do not check them as closely as message bodies. Calendar apps may also add the event on arrival. So the entry appears in a user’s schedule without them clicking anything.
Yes, on several platforms, because auto-adding is common. That default adds the event for you. An event can show up in your calendar whether or not you replied. Arrival does not mean you accepted it, and it does not mean anyone vetted it either.
Do not call any number in the invite, and do not follow its instructions. Report it through your one-click reporting route, then delete the entry. If it claims to come from a known contact, check through a channel you already use rather than replying.
Start with settings rather than training. Turn off auto-accept for invites. Limit outside invites where possible. Tag external entries visibly, and confirm your gateway inspects .ics attachments. Then add calendar lures to your simulation program.
Praveen Pal Singh is the Growth Director – North India & ASEAN at Threatcop, with experience spanning cybersecurity, business growth, and People Security Management. He works with organizations to address human-layer risks and strengthen their cybersecurity resilience. His areas of expertise include cybersecurity awareness, social engineering, phishing, email security, human risk management, and People Security Management. He is passionate about helping organizations build stronger, people-centric defenses against evolving cyber threats.
Automation handles volume, people handle judgment. See the difference between humans in, on, and out of the loop, and...
Attackers follow the news because crisis makes people act fast and check less. See the lure patterns and the...
The most common data breach is an employee emailing the wrong person. See the four parts of outbound email...
