Abandoned Outlook add-in hijacked to steal 4,000 logins
An Outlook add-in its developer had abandoned was still in Microsoft's store when an attacker took over its web address. Every add-in needs an owner.
Published · 3 min read

On 11 February 2026, BleepingComputer and The Hacker News reported findings by Koi Security about AgreeTo, a meeting-scheduling add-in for Outlook that had been listed in Microsoft's official store since December 2022. Its developer had abandoned it, and once the website it loaded from was deleted, an attacker claimed the address and used it to show a fake Microsoft sign-in page inside Outlook, collecting more than 4,000 Microsoft account credentials. Koi found the same attacker ran at least a dozen other phishing kits, and the stolen haul also held credit card numbers and banking security answers. By 12 February the add-in was gone from the store, and anyone who had installed it was advised to remove it and reset their password. Nobody had to break in anywhere: an add-in simply outlived the person who looked after it, and kept its access.
What Microsoft checked, and what it did not
An Outlook add-in is a small manifest file that names a web address, and Outlook loads whatever that address is serving at the time. Microsoft reviewed and signed AgreeTo's manifest in December 2022, pointing at outlook-one.vercel.app, and nothing checked what the address served after that. Its developer abandoned it around 2023 and, at some point after that, the deployment behind it was deleted, but the listing stayed, and so did the add-in's ReadWriteItem permission, which lets it read and change the user's mail. No use of that permission was confirmed. The stolen passwords left through a Telegram bot.
Koi called AgreeTo the first malicious Outlook add-in detected in the wild, and suggested that Microsoft re-review an add-in whenever the content at its address changes. Whatever the store does next, the lesson for an office is older than this case. The approval, the permission and the users' trust all outlived the developer, and the only thing that changed hands was a web address.
The add-ins nobody remembers installing
In Exchange Online, the mail service behind Microsoft 365, every user can install add-ins for their own use by default, according to Microsoft's documentation. So the add-ins in an office are whatever its staff have chosen over the years, each one running code from its developer's server with the permissions it was given on the day it was installed. The same question applies to every app connected to an office's mail, files or calendar, whoever provides them: who still maintains it, and who would notice if nobody did?
What it means for the systems I connect
Joining up what an office already uses is one of the things I focus on: HR systems, membership databases, QuickBooks, Stripe, Google Workspace and single sign-on, so that nothing is retyped. Each of those connections is an add-in by another name, code that reads from one system and often writes to another. They run in the client's own accounts, so the client holds the keys. What I would also want an office to hold is the list: what each connection reads and changes, why it was built, and who to call when it needs changing or switching off.
Five checks for the add-ins in your office
- List every Outlook add-in and connected app in use, with who uses it and who maintains it. One with no owner you can name is the first to remove.
- Decide who may install them. An administrator can take the My Marketplace Apps, My Custom Apps and My ReadWriteMailbox Apps roles out of Exchange Online's default role assignment policy, and install the approved add-ins for everyone instead.
- Read what each one is allowed to do. An add-in that can read and change mail should be doing a job that needs it.
- Remove what has gone quiet: no update in years, a developer who no longer answers, a website that has changed hands. AgreeTo had not been updated since December 2022.
- Keep the integrations built for you in your own accounts, with a note of what each one reads and writes, so the one that has outlived its purpose can be found and switched off.
If that list turns out longer than anyone expected, the fit check is a good place to start.
Sources
- BleepingComputer, Microsoft Store Outlook add-in hijacked to steal 4,000 Microsoft accounts, 11 February 2026
- The Hacker News, First Malicious Outlook Add-In Found Stealing 4,000+ Microsoft Credentials, 11 February 2026
- Microsoft Learn, Specify the administrators and users who can install and manage add-ins for Outlook in Exchange Online
Enrique Lacambra III builds internal business systems from Cainta, Rizal.
Tell me what is broken and I will tell you if it is worth building. A 20-minute call, no charge, and I will say so if you do not need me.
