Concrete signature match: Trojan - Appears legitimate but performs malicious actions for 64-bit Windows platform, family Rugmi
Trojan:Win64/Rugmi!rfn is a sophisticated 64-bit Trojan utilizing concrete evasion and persistence techniques. It abuses various Windows utilities like `mshta`, `regsvr32`, `rundll32`, BITS, PowerShell, and Scheduled Tasks for execution and stealth, while employing extensive API hooking for advanced malicious activities like process injection or system monitoring.
Relevant strings associated with this threat: - P:\fi\GPU\SSD\4o\switch\Synchronization\Buffer\oe\x86\debug\server\firm.pdb (PEHSTR_EXT) - U:\rout\x64\release\5bC\a2j\llq.pdb (PEHSTR_EXT) - \NewToolsProject\SQLite3Encrypt\Release\SQLite3Encrypt.pdb (PEHSTR_EXT) - rs-shell-main\kundalini (PEHSTR_EXT) - loader.pdb (PEHSTR_EXT) - !#HSTR:StringCodeForMshta.A!pli (PEHSTR_EXT) - !#HSTR:StringCodeForHooking.C!pli (PEHSTR_EXT) - !#HSTR:StringCodeForHooking.D!pli (PEHSTR_EXT) - !#HSTR:StringCodeForHooking.L!pli (PEHSTR_EXT) - !#HSTR:StringCodeForHooking.O!pli (PEHSTR_EXT) - !#HSTR:StringCodeForRegsvr32.A!pli (PEHSTR_EXT) - !#HSTR:StringCodeForRundll32.A!pli (PEHSTR_EXT) - rundll32 (PEHSTR_EXT) - !#HSTR:StringCodeForBITSJobs.A!pli (PEHSTR_EXT) - !#HSTR:StringCodeForPowerShell.G!pli (PEHSTR_EXT) - !#HSTR:StringCodeForScheduledTask.A!pli (PEHSTR_EXT) - !#HSTR:StringCodeForDataEncoding.D!pli (PEHSTR_EXT) - !#HSTR:StringCodeForHooking.J!pli (PEHSTR_EXT) - !#HSTR:StringCodeForHooking.K!pli (PEHSTR_EXT) - !#HSTR:StringCodeForRemoteFileCopy.B!pli (PEHSTR_EXT) - !#HSTR:ExecutionGuardrails (PEHSTR_EXT) - !#HSTR:StringCodeForFileDeletion.A!pli (PEHSTR_EXT) - !#HSTR:StringCodeForHooking.M!pli (PEHSTR_EXT) - !#HSTR:StringCodeForNetshHelperDLL.A!pli (PEHSTR_EXT) - !#HSTR:StringCodeForRemoteServices.A!pli (PEHSTR_EXT)
032d2462a90b19a43b3baff28e8df6678aecb6bbb406acd092a314abff06fcc8Immediately isolate the infected host. Perform a full system scan with updated security software to remove the detected threat. Manually inspect and remove any established persistence mechanisms (e.g., Scheduled Tasks, BITS jobs, registry modifications) and verify system integrity, especially for signs of API hooking. Consider a full system reimage to ensure complete eradication.