#Powershell Running in the background and using up high amount of Memory
29 messages · Page 1 of 1 (latest)
I might have found the task in the task scheduler.
In all active running tasks.
So after running for like 30min at 3gb memory it dialed down now.
Looks potentially malicious what does the task do?
google says it translates to Not available. Can't tell which column that is, requires more info
On my tasks, I have some values named unavoidable and disabled
@warped vapor as test, see if this works right
powershell -nop
You could check your profile, looking for anything strange
code $PROFILE
code $PROFILE.CurrentUserAllHosts
If you have SysInternals, there's process explorer
and even procmon if you need to catch it in action
So after running for like 30min at 3gb memory it dialed down now.
The time I had pwsh jump up to 4GBs in a few seconds was when I usedConvertTo-Jsonwith without limit onget-process
Used autorun and found the task, and also the ps1 file running it
That's the ps1 file and it's contents
The folder itself was created on 20.12.2022
I think it might be save to say to disable this task and delete the ps1 file
Looks like bad news
defintely
appears to be using the registry Computer\HKEY_LOCAL_MACHINE\SOFTWARE\dotnet
What would you recommend
I deleted the ps1 file and disabled the task under all active tasks on task scheduler.
If it's malware, and honestly I don't see any legitimate reason for that script and in that location then it can have done a bunch of stuff to stay resident on the system
It's building a script block, getting something from the registry and executes code
it's definitely obfuscated on purpose, whatever it does.
Trigger for the task was the login of an user.
Deleted now the task completely.
And also did a complete reboot, to see whatever another task pops up or if the powershell gets executed on their own again.
In the registry, do you see anything at ``HKEY_LOCAL_MACHINE\SOFTWARE\dotnet` ?
the first part checks this address
gp ('HKLM:\SOFTWARE\dotnetFLHyledR6')
property name might be 0b13tRNFAUL , can't tell with the font
Yeah found it
DotnetFLHyledR6
In the registry, going to delete it
not delete dotnet is fireworks for windows
Not dotnet, I deleted DotnetFLHyledR6 the newly created one from the malicious powershell scriptm
you need to work out when that was created and if it is on other machines in your org too and sharpish