Jump to content

duvkata

Members
  • Posts

    13
  • Joined

  • Last visited

Reputation

0 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Update: Upon restarting the computer, then uninstalling Node, then installing the latest version (was using 14.4.0, now I'm using 14.12.0 (very latest)) seems to fix the issue in VSCode, or at least I can't reproduce it as right now.
  2. I am using Microsoft Visual Studio Code, one of the most popular source-code editors out there. It has an option to open up a terminal window inside of the program, either cmd.exe, powershell or else. Well, today after I launched VSCode and the terminal inside, Malwarebytes detected both NodeJS and NPM as an exploit or "Malware.Exploit.Agent.Generic" to be exact. Now it says both files are quarantined and I need to restart my computer and NPM itself is no longer working. I believe this could have something to do with an NPM update I did yesterday, updated to 6.14.5, not sure what the previous version was, maybe 6.14.1. I remember reporting a very similar problem earlier this year, so I'm not sure why this problem is occurring again, especially since these tools and programs are used by millions of developers out there. I am attaching the logs from C:\ProgramData\Malwarebytes\MBAMService\AeDetections to this message. mbam.zip
  3. @AdvancedSetup thanks for your reply. I just want to mention that before you replied to me I used this Support Tool to perform a clean reinstallation. Unfortunately after doing that and restarting the computer, I tried replicating the issue with VSCode and it still exists. I am getting the same error even after clean install. --- That aside, I have run the tool and generated the logs zip archive. I am seeing that it contains some private information, so please let me know where I can send it to the support team privately (not on a public forum). There is an "Upload Logs" option available in the tool but it requires a ticket number and email. Thanks.
  4. Hi. Since very recently Visual Studio Code started throwing this error whenever I try to launch the integrated terminal: The terminal process command 'C:\Windows\system32\cmd.exe' failed to launch (exit code: {2}) For those unfamiliar, it basically opens command prompt inside of VSCode under the current project directory. I have been using this feature without a problem for years. I am using Windows 7 64 bit, and if I go to the system tray, right click on Malwarebytes and turn Ransomware protection off, it starts working again immediately, don't even need to restart VSCode. I tried to check my detection history to see if there was some log available -> Open Malwarebytes -> Detection History -> History but nothing there related to the issue. Also I just update to the latest version of Malwarebytes: - Malwarebytes version: 4.0.4.49 - Update package version: 1.0.18540 - Component package version: 1.0.810
  5. I just did and restarted VSCode but I am still getting the same error. I also tried adding the VSCode executable to the allow list as well but that doesn't work either.
  6. Hi. Since very recently Visual Studio Code started throwing this error whenever I try to launch the integrated terminal: The terminal process command 'C:\Windows\system32\cmd.exe' failed to launch (exit code: {2}) For those unfamiliar, it basically opens command prompt inside of VSCode under the current project directory. I have been using this feature without a problem for years. I am using Windows 7 64 bit, and if I go to the system tray, right click on Malwarebytes and turn Ransomware protection off, it starts working again immediately, don't even need to restart VSCode. I tried to check my detection history to see if there was some log available -> Open Malwarebytes -> Detection History -> History but nothing there related to the issue. Also I just update to the latest version of Malwarebytes: - Malwarebytes version: 4.0.4.49 - Update package version: 1.0.18540 - Component package version: 1.0.810
  7. Same stuff here. And upon restart it eats all my ram and web protection isn't even gonna turn on. What the hell is going on.
  8. I am having exactly the same problem. I have whitelisted several sites and none of them work. I don't even get block.malwarebytes I get a DNS error. This is all happening since the last update. Private/Incognito (no cache) doesn't make any difference. Please fix your software because right now mbam is as good as useless for me and I'm forced to disable web protection.
  9. Just updated Malwarebytes and now the exclusions are not working anymore. I have whitelisted several websites that I want to visit but instead of getting that block.malwarebytes.com message with the logo, I get this: When I disable Web Protection all the sites work fine. Mbam version is 3.0.6.1469 / 1.0.50 / 1.0.1137 and my account type is premium if thats of any importance.
  10. Just wanna add, I have run a scan on my wordpress installation and it found no problems at all. Also I ran this scanner: https://www.virustotal.com/en/url/37dae624052c14bd00937dd331460ae4278a8e67d86833f95835d0d20580bd0b/analysis/1476803029/ and malwarebytes is the only one that detects it as "suspicious". Please let me know why this is happening.
  11. Fraud stream, what does that mean? We aren't running any fraud on our website, there must be a mistake. It's just a website for videos, people come to watch and leave. Can you please tell me exactly which part/element/file on the website is considered fraud stream and if something isn't correct I`ll remove it?
  12. Hi, I'm getting 104.25.89.118, www.fullmatchesandshows.com blocked. https://i.gyazo.com/41a439b4b018870c4e2eb001ebb134cd.png I'm running Anti-malware Home (Premium) 2.2.1.1043. Can you please tell me what the issue with the website is and why it's getting blocked? Thanks in advance.
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.