YARA · BlackBerry Research & Intelligence (via Open-Source-YARA-rules)
BLACKBERRY_Mal_Infostealer_MSI_EXE_Jupyter_Certificate
Detects Jupter by certificate
- Autor
- BlackBerry Threat Research Team
- Datum
- 2021-11-04
- Geändert
- 2022-07-06
- Score / Qualität
- 75 / 83
Was diese Regel erkennt
Detects Jupter by certificate
Ziele: Windows-PE.
Sie definiert 16 Muster (12 Text, 1 Hex, 3 Regex).
Zusammenfassung aus den Metadaten und der Bedingung der Regel erzeugt.
Regelquelltext
rule BLACKBERRY_Mal_Infostealer_MSI_EXE_Jupyter_Certificate : FILE
{
meta:
= "Detects Jupter by certificate"
= "BlackBerry Threat Research Team"
= "837fdc85-d5ac-560b-bc49-6e34eb216e93"
= "2021-11-04"
= "2022-07-06"
= "https://blogs.blackberry.com/en/2022/01/threat-thursday-jupyter-infostealer-is-a-master-of-disguise"
= "https://github.com/mikesxrs/Open-Source-YARA-rules/blob/ec0056f767db98bf6d5fd63877ad51fb54d350e9/Blackberry/Mal_Infostealer_MSI_EXE_Jupyter_Certificate.yar#L1-L43"
= "N/A"
= "5524f227e4c0090b923d7966223806dd384458178083b752ebd9e0981b3fba52"
= 75
= 83
= "FILE"
= "This Yara rule is provided under the Apache License 2.0 (https://www.apache.org/licenses/LICENSE-2.0) and open to any user or organization, as long as you use it under this license and ensure originator credit in any derivative to The BlackBerry Research & Intelligence Team"
strings:
$msi = { D0 CF 11 E0 A1 B1 1A E1 }
$a1 = "EMCO MSI Package Builder"
$b1 = "powershell-ExecutionPolicy bypass -command \"iex([\\[]IO.File[\\]]::ReadAllText('[CurrentUserProfileFolder]" nocase
$b2 = "powershell-ep bypass -file \"[AppDataFolder]" nocase
$b3 = /powershell-ep bypass -windowstyle hidden -command \"\$xp=\'\[AppDataFolder\].{0,256}\.{0,256}\'/ nocase
$b4 = /powershell-ep bypass -windowstyle hidden -command \"\$p=\'\[AppDataFolder\].{0,256}\.{0,256}\'/ nocase
$b5 = /powershell-ExecutionPolicy bypass -command \"iex\(\[\\\[\]IO.File\[\\\]\]::ReadAllText\(\'\[CurrentUserProfileFolder\].{1,256}\..{1,256}\'\)\)/ nocase
$c1 = "OOO ENDI"
$c2 = "OOO MVS"
$c3 = "OOO LEVELAP"
$c4 = "Soto Manufacturing SRL"
$c5 = "Decapolis Consulting Inc."
$f1 = "SSL.com EV Root Certification Authority RSA R2"
$f2 = "SSL.com EV Code Signing Intermediate CA RSA R3"
$f3 = "DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1"
$f4 = "DigiCert Trusted Root G40"
condition:
($msi at 0 or uint16( 0 ) == 0x5a4d ) and all of ( $a* ) and 1 of ( $b* ) and 1 of ( $c* ) and 2 of ( $f* )
}
Strings (16 Muster)
| Bezeichner | Typ | Wert | Modifikatoren |
|---|---|---|---|
| $msi | Hex | { D0 CF 11 E0 A1 B1 1A E1 } | |
| $a1 | Text | "EMCO MSI Package Builder" | |
| $b1 | Text | "powershell-ExecutionPolicy bypass -command \"iex([\\[]IO.File[\\]]::ReadAllText('[CurrentUserProfileFolder]" | nocase |
| $b2 | Text | "powershell-ep bypass -file \"[AppDataFolder]" | nocase |
| $b3 | Regex | /powershell-ep bypass -windowstyle hidden -command \"\$xp=\'\[AppDataFolder\].{0,256}\.{0,256}\'/ | nocase |
| $b4 | Regex | /powershell-ep bypass -windowstyle hidden -command \"\$p=\'\[AppDataFolder\].{0,256}\.{0,256}\'/ | nocase |
| $b5 | Regex | /powershell-ExecutionPolicy bypass -command \"iex\(\[\\\[\]IO.File\[\\\]\]::ReadAllText\(\'\[CurrentUserProfileFolder\].{1,256}\..{1,256}\'\)\)/ | nocase |
| $c1 | Text | "OOO ENDI" | |
| $c2 | Text | "OOO MVS" | |
| $c3 | Text | "OOO LEVELAP" | |
| $c4 | Text | "Soto Manufacturing SRL" | |
| $c5 | Text | "Decapolis Consulting Inc." | |
| $f1 | Text | "SSL.com EV Root Certification Authority RSA R2" | |
| $f2 | Text | "SSL.com EV Code Signing Intermediate CA RSA R3" | |
| $f3 | Text | "DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1" | |
| $f4 | Text | "DigiCert Trusted Root G40" |
Bedingung
($msi at 0 or uint16( 0 ) == 0x5a4d ) and all of ( $a* ) and 1 of ( $b* ) and 1 of ( $c* ) and 2 of ( $f* )In Worten (Heuristik)
- Die Datei muss mit „MZ“ beginnen — eine Windows-Programmdatei (PE).
- Alle Muster aus ( $a* ) müssen treffen.
- Mindestens 1 Muster aus ( $b* ) müssen treffen.
- Mindestens 1 Muster aus ( $c* ) müssen treffen.
- Mindestens 2 Muster aus ( $f* ) müssen treffen.
- Muster $msi muss an Offset 0 stehen.
Diese Regel im Browser testen
Legen Sie eine Datei ab, um sie mit dieser Regel und YARA-X als WebAssembly zu scannen. Nichts wird hochgeladen.
Lizenz & Namensnennung
Autor: BlackBerry Threat Research Team
Quell-Repository: BlackBerry Research & Intelligence (via Open-Source-YARA-rules) @ ec0056f767
Lizenz: Apache License 2.0 (in den Metadaten der Regel angegeben)
“This Yara rule is provided under the Apache License 2.0 (https://www.apache.org/licenses/LICENSE-2.0) and open to any user or organization, as long as you use it under this license and ensure originator credit in any derivative to The BlackBerry Research & Intelligence Team”
Gespiegelt über YARA Forge 20260927, das Regelnamen mit der Quelle präfixiert und normalisierte Meta-Felder ergänzt.
Regel-ID: 837fdc85-d5ac-560b-bc49-6e34eb216e93
Tags:FILE
Verwandte Regeln
- MalwareBlackBerry Research & Intelligence (via Open-Source-YARA-rules)· BlackBerry Threat Research Team· 2022-04-06
- MalwareBlackBerry Research & Intelligence (via Open-Source-YARA-rules)· BlackBerry Threat Research Team· 2022-06-14
- MalwareBlackBerry Research & Intelligence (via Open-Source-YARA-rules)· BlackBerry Threat Research Team· 2022-06-14
- MalwareBlackBerry Research & Intelligence (via Open-Source-YARA-rules)· BlackBerry Threat Research Team· 2022-05-22
- MalwareBlackBerry Research & Intelligence (via Open-Source-YARA-rules)· BlackBerry Threat Research Team· 2022-05-22
- MalwareBlackBerry Research & Intelligence (via Open-Source-YARA-rules)· BlackBerry Threat Research Team· 2021-10-14
- MalwareBlackBerry Research & Intelligence (via Open-Source-YARA-rules)· BlackBerry Threat Research Team· 2021-11-09
- MalwareBlackBerry Research & Intelligence (via Open-Source-YARA-rules)· BlackBerry Threat Research Team· 2021-11-23