Windows 10: Trojan:MSIL/r77Rootkit.A!MTB and "Your credentials could not be verified"

Yurasianlynx68 · Jun 11, 2023

So these has been attacking me for 21 times but I've realized it only yesterday when my computer suddenly turned off and then went on....after that, the arrow is mostly with a loading. I tried the windows update but all it says is "Something went wrong. Try to reopen Setting later." And yet, the later never came. So when my computer locked because of inactivity for minutesthe normal thingy, but then it went, "Your credentials could not be verified." I pressed "Okay" ad then it went, "Something went wrong and your PIN isn't available status: Oxc000006d, substatus: Oxc0070070" so I tried to

:)

TSKYBing · Jun 11, 2023

Trojan and Malware

2/21/2022 5:28:49 AM

Files scanned: 1217349

Detected files: 43

Cleaned files: 43

Total scan time 06:50:37

Scan status: Finished

C:\$SysReset\AppxLogs\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\$SysReset\CloudImage\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\$SysReset\Logs\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\$SysReset\MDM\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\$SysReset\Scratch\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\$SysReset\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\Aomei\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\Boot\sm_da\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\Boot\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\FRST\Quarantine\C\WINDOWS\system32\Tasks\Microsoft\Windows\PI\PI.xBAD PowerShell/Kryptik.D trojan cleaned by deleting

C:\LDPlayer\LDPlayer4.0\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\LDPlayer\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\MobiMoverBackup\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\NVIDIA\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\OneDriveTemp\S-1-5-21-2131174034-2530422207-1368632259-1001\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\OneDriveTemp\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\Program Files\Wondershare\Wondershare Filmora\WsAP-Filmora.dll a variant of Win64/HackTool.Crack.W potentially unsafe application cleaned by deleting

C:\Program Files\Wondershare\Wondershare Filmora - Copy\WsAP-Filmora.dll a variant of Win64/HackTool.Crack.W potentially unsafe application cleaned by deleting

C:\Program Files (x86)\****-GoldBerg\****\OnlineFix64.dll a variant of Win64/HackTool.Crack.AA potentially unsafe application cleaned by deleting

C:\Riot Games\League of Legends\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\Riot Games\Riot Client\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\Riot Games\VALORANT\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\Riot Games\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\SWSetup\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\temp\TxGameDownload\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\temp\{AA7C2609-F5C3-4F2D-85D0-97C700C016B3}\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\temp\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\text\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\Users\TSKY\AppData\Local\VirtualStore\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\Users\TSKY\Desktop\Ready.Or.Not.v17900.Early.Access\Ready Or Not\ReadyOrNot\Binaries\Win64\Custom.dll a variant of Win64/HackTool.Crack.AD potentially unsafe application cleaned by deleting

C:\Users\TSKY\Desktop\Ready.Or.Not.v17900.Early.Access\Ready Or Not\ReadyOrNot\Binaries\Win64\OnlineFix64.dll a variant of Win64/HackTool.Crack.AA potentially unsafe application cleaned by deleting

C:\Users\TSKY\Downloads\Ready_or_Not_Fix_Repair_Steam_V3_Generic\ReadyOrNot\Binaries\Win64\Custom.dll a variant of Win64/HackTool.Crack.AD potentially unsafe application cleaned by deleting

C:\Users\TSKY\Downloads\Ready_or_Not_Fix_Repair_Steam_V3_Generic\ReadyOrNot\Binaries\Win64\OnlineFix64.dll a variant of Win64/HackTool.Crack.AA potentially unsafe application cleaned by deleting

C:\Users\TSKY\Downloads\Windows 10_Digital_License\BIN\slc.dll Win32/HackTool.WinActivator.AL potentially unsafe application cleaned by deleting

C:\Users\TSKY\Downloads\Windows 10_Digital_License\Windows 10 Digital License Activation Script.cmd Win32/HackTool.WinActivator.AI potentially unsafe application cleaned by deleting

C:\Users\TSKY\Downloads\BrowserSetup_b0zz0i5.exe a variant of Win32/CryptoTab.A potentially unwanted application cleaned by deleting

C:\Users\TSKY\Downloads\counter-strike-1-6.exe a variant of Win32/GameHack.ANF potentially unsafe application cleaned by deleting

C:\Users\TSKY\Downloads\windows.cmd BAT/RiskWare.HackTool.WinActivator.A application cleaned by deleting

C:\Users\TSKY\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\Windows \System32\_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\Windows \_readme.txt MSIL/Filecoder.ANG trojan deleted

C:\Xamp Premium\_readme.txt MSIL/Filecoder.ANG trojan deleted

D:\_readme.txt MSIL/Filecoder.ANG trojan deleted

Camille Maloloy-on · Jun 11, 2023

windows defender detects but cant remove Trojan msil crypinject C!MIL.....

C:\Users\Admin\Downloads\krnl\krnlss.exe

Trojan msil cryptinject C!MIL

I cant get windows defender to remove/quarantine this virus, any help would be appreciated.

Brink · Jun 11, 2023

Credential Guard lab companion

If you have heard about Credential Guard in Windows Server 2016 (and in Windows 10), but do not have an environment to try it out, here is a lab environment we built for you to play.

Lab access

The link will lead you to a sign up page, after that, you will see the following labs listed for Windows Server 2016:

Windows Server 2016 labs

There are 3 exercises in the “Implementing Breach Resistance Security in Windows Server 2016”:

Credential Guard

Remote Credential Guard

Device Guard

This blogpost will walk you through the Credential Guard lab details.

After click on the link of Breach Resistance lab, you be required to sign in and then you can launch the lab:

Sign-in

Launch page

It takes a few minutes to create the VMs, and once it has done, you will see the following machines prepared:

Initialize

DC: domain controller, which is not used for this exercise.

SRV01 and SRV02: both are Windows Server 2016, and used for the lab exercise.

Lab exercise – Explained

The steps are listed in the Content section:

Content

This lab is structured to cover the following in sequence:

Understand how attackers can use the hash in memory to gain access to domain controllers

Configure Credential Guard

Verify the hash in memory is protected using Credential Guard

You can follow the steps listed under the content section to complete the lab, the intent of the blog, is to break the procedures into groups, to help you understand the exercise better.

Prep the hash

Lsass.exe is the process which handles user logon, it stores the user credential information in its memory. The memory is cleared when the machine starts up. In this lab environment, all the virtual machines start at the time lab launches, when you logon to the machine, you will only have the logon user credential information in memory. In order to demonstrate an attacker gaining user access using other account’s hash, the first part of the lab is to simulate a server which has been running for a while, different users had remotely or locally connected to it, therefore, lsass memory stored many different user credential information.
This is accomplished by step 1-8.

Retrieving credential hash

Mimikatz is a popular tool for retrieving lsass memory information. The tool has been copied to the lab machines, step 9-13 walk you through the process of dumping lsass memory using Mimikatz.

Pass the Hash

Pass the hash is a hacking technique that allows an attacker to authenticate by using the underlying NTLM, instead of specifying the user password. In step 14 to 24, you will extract LabAdmin hash from lsass using Mimikatz, and use the hash to open a PowerShell console, and perform a couple of operations using the LabAdmin privilege:

Add a user to the domain admin group

Open remote PowerShell connection to a domain controller

Both operations could not be performed by the logon user. But using the hash of the LabAdmin, an attacker will be able to do it using the information retrieve from Lsass memory.

Configure and verify Credential Guard

Step 25 to 36 illustrate the steps to configure credential guard, then verify its status using msinfo32.exe and PowerShell.

Step 37 to 43 goes further to use Mimikatz to show the hash in Lsass is now encrypted using Credential Guard.

More info

The exercise illustrated the benefit of Credential Guard in Windows Server 2016 as well as Windows 10. For more information, you can find here.
Click to expand...

Source: Credential Guard lab companion Datacenter and Private Cloud Security Blog

See also:

Enable or Disable Credential Guard in Windows 10 Windows 10 Security System Tutorials

Verify if Credential Guard is Enabled or Disabled in Windows 10 Windows 10 Security System Tutorials

Windows 10: Trojan:MSIL/r77Rootkit.A!MTB and "Your credentials could not be verified"

Trojan:MSIL/r77Rootkit.A!MTB and "Your credentials could not be verified"

Trojan:MSIL/r77Rootkit.A!MTB and "Your credentials could not be verified"

Trojan:MSIL/r77Rootkit.A!MTB and "Your credentials could not be verified"

Trojan:MSIL/r77Rootkit.A!MTB and "Your credentials could not be verified" - Similar Threads - Trojan MSIL r77Rootkit

Your credentials could not be verified

“Your credentials could not be verified”

Trojan: MSIL/AgentTesla.BFV!MTB

Trojan: MSIL/AgentTesla.BFV!MTB

Trojan:MSIL/r77Rootkit.A!MTB and "Your credentials could not be verified"

"Your credentials could not be verified"

Your credentials could not be verified.

Your credentials could not be verified.

Your credentials could not be verified