Jump to content

Suspected False Positive While Debugging in Visual Studio .NET


Recommended Posts


I was firing up a debug session in Visual Studio .NET a bit earlier today, and Malwarebytes popped up telling me it detected and blocked a Ranson attack.  The debug session failed, and I got a warning inside Visual Studio about an inability to access a file it was trying to access as it completed a software build prior to launching the debugger.

Here's the summary:


-Log Details-
Protection Event Date: 2/20/20
Protection Event Time: 5:35 PM
Log File: 31127742-5431-11ea-a0a1-00059a3c7800.json

-Software Information-
Components Version: 1.0.823
Update Package Version: 1.0.19514
License: Premium

-System Information-
OS: Windows 7 Service Pack 1
CPU: x64
File System: NTFS
User: System

-Ransomware Details-
File: 1
Malware.Ransom.Agent.Generic, C:\USERS\ANDY\APPDATA\LOCAL\TEMP\TMPDFCFDA62207242EBBA421712C36D2791.EXEC.CMD, Quarantined, 0, 392685, 0.0.0


I suspect this was a false positive and that the file produced was part of the VS.NET build process.  But I don't really know it for a fact.  

How can I help you guys determine if this was a false positive or not?





Link to post
Share on other sites

I followed the directions in the link you posted and responded to the email you sent by attaching the MBST log.  As mentioned in my email reply, the file in question no longer exists on my system.  If it's part of the normal VS.NET build process, then it makes sense that it's auto-deleted after the build completes.  

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • 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.