Classe: Packed
Os programas mal-intencionados são freqüentemente compactados - ou compactados - usando uma variedade de métodos combinados com criptografia de arquivos para evitar engenharia reversa do programa e para impedir a análise do comportamento do programa com métodos proativos e heurísticos. Programas antivírus detectam os resultados das ações de empacotadores suspeitos, isto é, itens empacotados. Existem maneiras de impedir que arquivos compactados sejam descompactados: por exemplo, o empacotador não pode decifrar o código totalmente, apenas na medida em que é executado; ou pode descriptografar e iniciar um programa mal-intencionado somente em um determinado dia da semana. Os principais recursos que diferenciam os comportamentos da subclasse Suspicious Packers são o tipo e o número de empacotadores usados no processo de compactação de arquivos.Plataforma: Win32
O Win32 é uma API em sistemas operacionais baseados no Windows NT (Windows XP, Windows 7, etc.) que oferece suporte à execução de aplicativos de 32 bits. Uma das plataformas de programação mais difundidas do mundo.Família: Packed.Win32.Katusha
No family descriptionExamples
EAA5766D6704C2D42E6A15C78E78675EDC51D6FAEF2FC1C2CD7C4CD9734854B3
13291E3024B4A4860276D2A881E3DAEB
27C86A5ED09761AAF69FB25E438AE778
13C637D26A9247F51E40503CABC553AC
Tactics and Techniques: Mitre*
TA0002
Execution
The adversary is trying to run malicious code. Execution consists of techniques that result in adversary-controlled code running on a local or remote system. Techniques that run malicious code are often paired with techniques from all other tactics to achieve broader goals, like exploring a network or stealing data. For example, an adversary might use a remote access tool to run a PowerShell script that does Remote System Discovery.
T1203
Exploitation for Client Execution
Adversaries may exploit software vulnerabilities in client applications to execute code. Vulnerabilities can exist in software due to unsecure coding practices that can lead to unanticipated behavior. Adversaries can take advantage of certain vulnerabilities through targeted exploitation for the purpose of arbitrary code execution. Oftentimes the most valuable exploits to an offensive toolkit are those that can be used to obtain code execution on a remote system because they can be used to gain access to that system. Users will expect to see files related to the applications they commonly used to do work, so they are a useful target for exploit research and development because of their high utility.
T1204.002
User Execution: Malicious File
An adversary may rely upon a user opening a malicious file in order to gain execution. Users may be subjected to social engineering to get them to open a file that will lead to code execution. This user action will typically be observed as follow-on behavior from Spearphishing Attachment. Adversaries may use several types of files that require a user to execute them, including .doc, .pdf, .xls, .rtf, .scr, .exe, .lnk, .pif, and .cpl.
Adversaries may employ various forms of Masquerading and Obfuscated Files or Information to increase the likelihood that a user will open and successfully execute a malicious file. These methods may include using a familiar naming convention and/or password protecting the file and supplying instructions to a user on how to open it.(Citation: Password Protected Word Docs)
While Malicious File frequently occurs shortly after Initial Access it may occur at other phases of an intrusion, such as when an adversary places a file in a shared directory or on a user's desktop hoping that a user will click on it. This activity may also be seen shortly after Internal Spearphishing.
Adversaries may employ various forms of Masquerading and Obfuscated Files or Information to increase the likelihood that a user will open and successfully execute a malicious file. These methods may include using a familiar naming convention and/or password protecting the file and supplying instructions to a user on how to open it.(Citation: Password Protected Word Docs)
While Malicious File frequently occurs shortly after Initial Access it may occur at other phases of an intrusion, such as when an adversary places a file in a shared directory or on a user's desktop hoping that a user will click on it. This activity may also be seen shortly after Internal Spearphishing.
* © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation.