Loading malware…
Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.
3 distinct techniques documented for this family, organized by ATT&CK tactic.
PowerShdll allows PowerShell to run through: rundll32.exe DLL exports Reflective loading Unmanaged execution paths ... Instead of spawning powershell.exe, the PowerShell engine runs inside rundll32.exe.
PowerShdll allows PowerShell to run through: rundll32.exe DLL exports Reflective loading Unmanaged execution paths | This allows adversaries to: Avoid detections tied to powershell.exe Blend into trusted processes Evade command-line monitoring Reduce PowerShell logging visibility Execute PowerShell in-memory
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An open-source PowerShell execution utility (here modified by the attackers) used to run PowerShell code without invoking powershell.exe, likely as a post-compromise execution/defense-evasion aid.
A modified version of the open-source PowerShdll tool customized by the attackers to expose a single export routine that accepts a string and passes it to PowerShell DLLs for interpretation, returning the result.
A modified version of the open-source PowerShdll tool customized by the attackers to expose a single export routine that accepts a string and passes it to PowerShell DLLs for interpretation, returning the result.
Match every observed IP, domain, and hash against your live telemetry.
Named campaigns wielding this family, with evidence pinned to each claim.
CVEs this family uses for access and lateral movement.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Every documented technique, ranked by evidence weight.
Reddit, Mastodon, and CTI community discussion around this family.