The sample 5e56a3c4d4c304ee6278df0b32afb62bd0dd01e2a9894ad007f4cc5f873ab5cf (PowerLoader) fails to detonate properly with 64-bit capemon compiled with VS2022 on Windows 7 x64.
The issue appears to be with the WriteProcessMemory hook which is called early in capture of the injected explorer.exe. Even with an 'empty' hook detonation fails.
If capemon is compiled with VS2017 the sample detonates fine, as seen below:
The sample
5e56a3c4d4c304ee6278df0b32afb62bd0dd01e2a9894ad007f4cc5f873ab5cf(PowerLoader) fails to detonate properly with 64-bit capemon compiled with VS2022 on Windows 7 x64.The issue appears to be with the
WriteProcessMemoryhook which is called early in capture of the injectedexplorer.exe. Even with an 'empty' hook detonation fails.If capemon is compiled with VS2017 the sample detonates fine, as seen below: