This rule detects the presence of the Packanoidv1Arkanoid YARA signature, which identifies specific malicious or packed code artifacts that adversaries may use to obscure their presence on endpoints. Proactively hunting for this low-severity indicator allows the SOC team to identify early-stage infections or dormant payloads in Azure Sentinel, enabling rapid triage before they escalate into more complex compromise scenarios.
rule Packanoidv1Arkanoid
{
meta:
author="malware-lu"
strings:
$a0 = { BF [4] BE [4] E8 9D 00 00 00 B8 [4] 8B 30 8B 78 04 BB [4] 8B 43 04 91 E3 1F 51 FF D6 56 96 8B 13 8B 02 91 E3 0D 52 51 56 FF D7 5A 89 02 83 C2 04 EB EE 83 C3 08 }
condition:
$a0 at pe.entry_point
}
This YARA rule can be deployed in the following contexts:
This rule contains 1 string patterns in its detection logic.
Scenario: A developer or DevOps engineer uses 7-Zip or WinRAR to compress a large source code directory or log archive for backup purposes. The resulting .zip or .rar file contains specific binary structures or compression artifacts that match the Packanoidv1Arkanoid signature, particularly if the archive contains mixed file types or is created with specific compression levels.
.zip, .rar, .7z, and .tar.gz located in standard backup directories (e.g., C:\Backups\, \\fileserver\backups\) or when the parent process is a known archiving tool like 7z.exe, WinRAR.exe, or tar.exe.Scenario: An IT administrator runs Veeam Backup & Replication or Commvault to perform a full backup of a virtual machine or physical server. The backup software creates large, complex archive files that may inadvertently trigger the YARA rule due to their internal structure or embedded metadata.
VeeamBackup.exe, CommvaultAgent.exe) and files located in designated backup repositories (e.g., C:\Veeam\Backups\, D:\Commvault\).Scenario: A software deployment tool like Chocolatey or WSUS downloads and installs a package that includes a compressed installer or a .cab file. The .cab file or the temporary extracted archive may match the Packanoidv1Arkanoid pattern, especially if the package contains legacy components or specific binary resources.
.cab and .msi when the parent process is a package manager (choco.exe,