ActiveMime
From Just Solve the File Format Problem
(Difference between revisions)
Ross-spencer (Talk | contribs) (Initial commit of the undocumented format from Microsoft using information on https://github.com/phishme) |
Dan Tobias (Talk | contribs) |
||
| Line 1: | Line 1: | ||
| + | {{FormatInfo | ||
| + | |formattype=electronic | ||
| + | |subcat=Document | ||
| + | |extensions={{ext|mso}} | ||
| + | |mimetypes={{mimetype|application/x-mso}} | ||
| + | }} | ||
Documented by [https://github.com/phishme phishme] on GitHub, ActiveMime is an undocumented Microsoft file format often seen used to encode Microsoft Office Macros. | Documented by [https://github.com/phishme phishme] on GitHub, ActiveMime is an undocumented Microsoft file format often seen used to encode Microsoft Office Macros. | ||
Revision as of 03:30, 8 June 2016
Documented by phishme on GitHub, ActiveMime is an undocumented Microsoft file format often seen used to encode Microsoft Office Macros.
ActiveMime binary objects may reside in Microsoft Web Archive (MHT) files documented by Cyren.
There is little official documentation that can be searched for. The earliest references indexed by Google seem to come from 2012 but not much earlier.
There is more information and a further call for collaboration or corrections on what is documented on the Pishme GitHub README.
Magic Number
The structure is partially reversed engineered by phishme on GitHub. Once decoded from Base64 the magic number of the format is: 41 63 74 69 76 65 4d 69 6d 65 00 00 - 'ActiveMime' + null terminators.
Other Links
- Python Amime: Library for working with ActiveMime
- XML: A New Vector For An Old Trick describing malware distribution with an ActiveMime binary payload
- Evolution of Dridex
- Decalage Python code for extracting data from ActiveMime
- Cyren Article on ActiveMime
- Malicious Macros Evades Detection Using Unusual File Format
- Early MSDN forum post asking about ActiveMime
