Classe: Trojan-PSW
Les programmes Trojan-PSW sont conçus pour dérober des informations de compte d'utilisateur telles que les connexions et les mots de passe des ordinateurs infectés. PSW est un acronyme de Password Stealing Ware. Lorsqu'il est lancé, un cheval de Troie PSW recherche les fichiers système qui stockent une série de données confidentielles ou le registre. Si de telles données sont trouvées, le cheval de Troie l'envoie à son «maître». L'email, le ftp, le Web (y compris les données dans une demande), ou d'autres méthodes peuvent être utilisés pour passer les données volées. Certains de ces chevaux de Troie volent également des informations d'enregistrement pour certains logiciels.Plus d'informations
Plateforme: MSIL
Le Common Intermediate Language (anciennement connu sous le nom de Microsoft Intermediate Language, ou MSIL) est un langage intermédiaire développé par Microsoft pour le .NET Framework. Le code CIL est généré par tous les compilateurs Microsoft .NET dans Microsoft Visual Studio (Visual Basic .NET, Visual C ++, Visual C # et autres).Famille: Trojan-PSW.MSIL.Reline
No family descriptionExamples
F2B80B334950BAC8F5E0E3CDAD1F07ABC4C5EB9235C6D88498CA965FC037AF8B
E01738AF73166BA4B4CEECAE21A58A1C
DBC405468B999D6E231FC33AD260F744
DBCB044DC3629CF19E2635156AB42E4C
Tactics and Techniques: Mitre*
TA0005
Defense Evasion
The adversary is trying to avoid being detected.
Defense Evasion consists of techniques that adversaries use to avoid detection throughout their compromise. Techniques used for defense evasion include uninstalling/disabling security software or obfuscating/encrypting data and scripts. Adversaries also leverage and abuse trusted processes to hide and masquerade their malware. Other tactics’ techniques are cross-listed here when those techniques include the added benefit of subverting defenses.
Defense Evasion consists of techniques that adversaries use to avoid detection throughout their compromise. Techniques used for defense evasion include uninstalling/disabling security software or obfuscating/encrypting data and scripts. Adversaries also leverage and abuse trusted processes to hide and masquerade their malware. Other tactics’ techniques are cross-listed here when those techniques include the added benefit of subverting defenses.
T1055.012
Process Injection: Process Hollowing
Adversaries may inject malicious code into suspended and hollowed processes in order to evade process-based defenses. Process hollowing is a method of executing arbitrary code in the address space of a separate live process.
Process hollowing is commonly performed by creating a process in a suspended state then unmapping/hollowing its memory, which can then be replaced with malicious code. A victim process can be created with native Windows API calls such as
This is very similar to Thread Local Storage but creates a new process rather than targeting an existing process. This behavior will likely not result in elevated privileges since the injected process was spawned from (and thus inherits the security context) of the injecting process. However, execution via process hollowing may also evade detection from security products since the execution is masked under a legitimate process.
Process hollowing is commonly performed by creating a process in a suspended state then unmapping/hollowing its memory, which can then be replaced with malicious code. A victim process can be created with native Windows API calls such as
CreateProcess, which includes a flag to suspend the processes primary thread. At this point the process can be unmapped using APIs calls such as ZwUnmapViewOfSection or NtUnmapViewOfSection before being written to, realigned to the injected code, and resumed via VirtualAllocEx, WriteProcessMemory, SetThreadContext, then ResumeThread respectively.(Citation: Leitch Hollowing)(Citation: Elastic Process Injection July 2017)This is very similar to Thread Local Storage but creates a new process rather than targeting an existing process. This behavior will likely not result in elevated privileges since the injected process was spawned from (and thus inherits the security context) of the injecting process. However, execution via process hollowing may also evade detection from security products since the execution is masked under a legitimate process.
* © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation.