1-minute read of a 4 min report

NeedyMantis Uses Sideloaded DLLs to Maintain Windows Access

By

1-minute read

What a defender needs to know

Microsoft Threat Intelligence reports NeedyMantis in a limited number of targeted intrusions affecting telecoms, universities, medical nonprofits, intergovernmental organizations and government contractors. The malware arrives after the attacker has access. A legitimate Windows program loads a substituted DLL from its folder; that DLL extracts another loader from a neighboring extensionless archive with the same basename. The analyzed Poedit pair is WinSparkle.dll and WinSparkle.

Search file and process telemetry for the loader beside Poedit, curl, Vim or TightVNC software, then check for the paired archive, its hash and network-share copy activity. Microsoft’s analyzed loader SHA-256 is e842dd7642c8e04b5ec20b6393848a9c904e4832930950c16664fe7800ba382e. Correlate any outbound traffic to corp[.]tripswithengine[.]com with the initiating process. Corroborate a DLL filename or the reported firefox/21.0 user agent with the matching archive, process and network activity.

Isolate matching hosts, block the identified destination, preserve telemetry and trace the account and share used to move the files. Verify that cloud-delivered protection, EDR in block mode and network protection apply to those devices, and check for new destination connections or a reappearing loader/archive pair. Investigate the original access route too: Microsoft’s observed NeedyMantis deployments followed prior compromise, and that route can outlast removal of the implant.

Primary sources