https://www.botnets.fr/index.php?action=history&feed=atom&title=Flamer_analysis%3A_framework_reconstructionFlamer analysis: framework reconstruction - Revision history2026-10-24T02:11:25ZRevision history for this page on the wikiMediaWiki 1.43.11https://www.botnets.fr/index.php?title=Flamer_analysis:_framework_reconstruction&diff=2354&oldid=prevEric.freyssinet: 1 revision imported2015-02-07T14:27:14Z<p>1 revision imported</p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 14:27, 7 February 2015</td>
</tr><tr><td colspan="4" class="diff-notice" lang="en"><div class="mw-diff-empty">(No difference)</div>
</td></tr>
<!-- diff cache key wiki:diff:1.41:old-2353:rev-2354 -->
</table>Eric.freyssinethttps://www.botnets.fr/index.php?title=Flamer_analysis:_framework_reconstruction&diff=2353&oldid=prevEric.freyssinet: Remplacement du texte — « Eset » par « ESET »2012-08-19T17:53:38Z<p>Remplacement du texte — « Eset » par « ESET »</p>
<p><b>New page</b></p><div>{{Publication<br />
|Image=Flamer analysis framework reconstruction.png<br />
|Legend=<br />
|Document=<br />
|Licence=<br />
|Video=<br />
|Link=http://blog.eset.com/2012/08/02/flamer-analysis-framework-reconstruction blog.eset.com<br />
|Author=Aleksandr Matrosov, Eugene Rodionov, <br />
|NomRevue=ESET Threat Blog<br />
|Date=Aug 2, 2012<br />
|Editor=ESET<br />
|Year=2012<br />
|ISBN=<br />
|Page=<br />
|Abstract=From the very beginning of our analysis of Win32/Flamer it was clear that this was an extremely sophisticated piece of malware which we had never seen before. It implements extremely elaborate programming logic and has an intricate internal structure. At the heart of Flame’s modularity lies a carefully designed architecture allowing all its components interoperability without causing any incompatibilities. In this blog post we will concentrate mainly on the internal architecture of the mssecmgr.ocx module (Flame, Duqu and Stuxnet: in-depth code analysis of mssecmgr.ocx). In the course of our research we analysed several different versions of mssecmgr.ocx and found specific architectural similarities that allow us to reconstruct Flame’s framework.<br />
|Botnet=Flame, <br />
|Malware=, <br />
|CCProtocol=, <br />
|Operation=, <br />
|Keyword=, <br />
}}</div>Eric.freyssinet