The aim of this project is to reverse engineer the Outlook desktop app to find a way to block the ads. This is a work in progress, so don't expect anything. I am in no way experienced in reverse engineering, so if you have any tips, please let me know.
-
Q: Why?
A: I like outlook. I use it a lot, personally and for work. I don't like ads. I want to block them. Also I want to learn more about reverse engineering.
-
Q: What is the goal of this project?
A: To find a way to block the ads in the Outlook desktop app, without breaking the app and removing the blank space where the ads would be.
-
Q: What tools are you using?
A: I am using Process Hacker to view the threads and Ghidra to reverse engineer the app.
- Ads are loaded from
https://outlookads.live.com/
When the app is opened, everything is rendered using the Microsoft Edge WebView2 (msedgewebview2.exe) with the render ID's 1-6. The ads are rendered in the render ID 7. This thread gets created when switching to the tab containing the ads.
"The Microsoft Edge WebView2 control allows you to embed web technologies (HTML, CSS, and JavaScript) in your native apps. The WebView2 control uses Microsoft Edge as the rendering engine to display the web content in native apps."
For us, this means that the ads loaded in some way of HTML, CSS or JavaScript. After checking the filesystem, I couldn't find any files that loaded the ads. This means that the ads are probably loaded from the internet. But things get more interesting when checking the strings loaded into the memory of the msedgewebview2.exe process, with the render ID 7.
Here we can see the string adsframe repeated again and agains, as well as the MS office CDN link to the javascript file responsible for loading the ads. Check out adsframe.js for a beautified version of the file.
While this is very important, I haven't found anything too interesting in the 30K lines of code.
But what could be very important is the last memory address 0x38f00160c00c. At this address we can see the beginning of the entire adsframe.js file. That means that the code is loaded into the memory somewhere around there.
Also interesting is the optout string. This probably means that there is a way to opt out of the ads, but I couldn't figure out what the needed payload is. When accessing the site directly, it just loops the outlook startup animation, without anything else happening.
--renderer-client-id=7--webview-exe-name=olk.exe
- None found (yet)
Here are some approaches that I've tried, but didn't work out to the extend that I wanted them to.
- Blocking the URL in the hosts file. This works, but still leaves a blank space where the ads would be. See this repo for more info.
-
Pausing the render ID 7 thread. This works, but also leaves the blank space behind. See barblock.py for a PoC.
-
Killing the render ID 7 thread. Sadly, this also kills the whole app, making it unusable.
Here are some suggestions, that I got from other people (mostly Discord). I haven't tried them yet, but I will in the future. Feel free to suggest more!
- Find the function that loads the
adsframe.jsand make it return nothing or point it to a custom server that returns a blank javascript file.
In this repo included is my current Ghidra project file. This contains the older OUTLOOK.EXE, which is the base outlook with most of the features and the newer OLK.EXE, which is the new UI with the ads.
ALso included is the barblock.py file, which is a PoC for the background thread blocking approach.
Pull requests are VERY welcome. I am not experienced in reverse engineering, so any help is appreciated. For major changes, please open an issue first to discuss what you would like to change.
This repository is for research purposes only, the use of this code is your responsibility.
I take NO responsibility and/or liability for how you choose to use any of the source code available here. By using any of the files available in this repository, you understand that you are AGREEING TO USE AT YOUR OWN RISK. Once again, ALL files available here are for EDUCATION and/or RESEARCH purposes ONLY.