Before following an AI event invitation, find the event independently on the organizer's official website, match its registration destination, and check what any sign-in request authorizes. A familiar short-link domain, a polished registration page or even a genuine Microsoft login page cannot establish all three things for you.
This guide is for creators and marketing teams receiving webinar invitations, and for organizers sharing their own registration links. It is a verification checklist, not a claim that every short link or work-account sign-in is suspicious.
Why revisit event links now?
On November 5, 2026, Push Security published research into fake OpenAI, SpaceX and Anthropic event pages. Its investigation describes familiar short-link services leading toward imitation registration pages, followed by Microsoft device-code phishing or proxied Google sign-ins. The brands were impersonated; this does not establish a breach of those companies.
BleepingComputer reported the campaign on November 5, including the use of short links and the two authentication paths. That reporting draws on Push's investigation, rather than constituting a second independent detection. This is recent November research, not an announcement first published this week. We have not visited the malicious infrastructure or reproduced the attack.
1. Confirm the event without relying on the invitation
Open the organizer's known website from a bookmark or an address you already trust. Look for its event listing and compare the title, date, time zone, speakers and registration provider. If a search is necessary, inspect the destination before opening a result; a sponsored result is not proof of organizer identity.
An invitation can be legitimate even when it is private and absent from a public calendar. In that case, ask a known organizer contact through an established channel. Do not use only the contact details supplied by the questionable invitation. Keep registration on hold until the organizer confirms the exact destination and expected login process.
Example: a fictional invitation promises an AI marketing workshop and a free subscription. Your campaign spreadsheet has a row for the organizer, official event page, registration host and verification date. If the official site confirms the workshop but says nothing about the subscription, record the reward as unverified. Do not let the attractive part of the invitation stand in for verification of the whole offer.
2. Separate the shared address from the destination
A short link is an entrance that can redirect somewhere else. Confirming who operates that entrance does not confirm who created this particular link or who controls its destination. A branded URL can make an organizer's communications more recognizable, but recognition is not an identity guarantee.
For an invitation you have not verified, prefer the registration route linked from the official event page. Do not explore a suspicious redirect chain in your everyday signed-in browser just to see where it ends. A preview or URL scanner can provide information, but a clean result is not proof of safety. Do not submit private invitation tokens to public scanning services; ask your security team to inspect them using approved tools.
After reaching the independently confirmed registration service, compare the full hostname with the organizer's instructions. In an illustrative address such as organizer.example.net, the word “organizer” alone does not establish ownership. Stop if the host, event details or requested action changes unexpectedly. A certificate and an HTTPS connection do not validate the event's promise.
3. Check the authorization, not just the login logo
Microsoft's April 6 security research explains the important distinction: in device-code phishing, someone else initiates a sign-in and persuades the victim to authorize it. Authentication can occur on the real Microsoft site while granting access to the attacker's session. This older source explains the mechanism; it is not evidence of a new November incident.
If an event page tells you to copy a device code into a login page to claim a reward, pause. Verify the purpose with the organizer and your workplace IT team before entering or approving it. Do not approve an app or device that you did not intend to authorize. A successful password or MFA check answers an authentication question; it does not establish that this authorization serves your intended task.
| What you see | What it establishes | What to check next |
|---|---|---|
| Recognizable short URL | An address on that domain | The organizer and intended destination |
| Matching event branding | The page displays those assets | An independent official event listing |
| Genuine sign-in page | The identity provider is handling authentication | The app, device and access being authorized |
| Registration confirmation | The service recorded a submission | That the service belongs to the verified event |
4. Make your own invitations easier to verify
Publish a stable event page on your organization's site. Name any external registration provider there and explain whether attendees need an account, which provider handles sign-in, and why. Include a contact reachable through your existing website. Use the same event title and time zone in the invitation, landing page and confirmation.
If you use 302.sh for distribution, point the short link to that verified page and record who maintains it. An editable destination is useful when a registration page moves; after an edit, recheck the original shared address. Our event registration QR guide covers keeping printed entrances useful when plans change. A QR code provides another entrance, not a separate trust guarantee.
Before sending, have a colleague follow the intended registration route without the organizer's existing login. Ask them to describe the event and any access requested. This checks clarity and the normal customer journey; it is not a penetration test or proof that the service cannot be compromised. Avoid unsupported “verified safe” badges or promises that a branded link prevents phishing.
If you already approved an unexpected request
Stop interacting with the invitation and contact your workplace security or IT team through its established channel. Preserve the original message, URL and approximate time privately. Tell them whether you merely opened the page, entered credentials, pasted a device code, or approved access; those are different exposure states. Do not forward an active suspicious link to colleagues as a test.
Follow the account provider's recovery process with your administrator. Microsoft's guidance includes revoking affected sessions and investigating access; changing a password alone should not be treated as a completed response to token theft. This checklist does not determine whether an account was compromised.
Where short-link management fits
302.sh helps you maintain and share destinations you control. It does not certify third-party events, validate their rewards, or determine whether a Microsoft or Google authorization is appropriate. Link reports also cannot establish that a visitor registered safely. For a related measurement boundary, read why an email link can get clicks before a person reads it.
The useful handoff is simple: a confirmed organizer, a documented registration destination, an understood authorization, and someone responsible for changes. If one of those remains unknown, keep the invitation unverified.
What is included in 302.sh?
Free allows 5 new links per UTC month and up to 50 owned links, with 5 custom slugs per month of at least 6 characters. Deleting a link does not refund its monthly creation allowance.
Free includes 2,000 analytics events per month and 90-day retention. Reaching that analytics allowance stops additional tracking, not redirects. Link deletion, owner-set limits and safety enforcement can still stop redirects. Branded domains require a paid plan and completed domain setup. See current plans and limits.
Try the workflow
Explore the dashboard demo, or create a short link using a destination you own or are authorized to share. Verify the destination before distributing it.



