Jump to content

oyug

Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by oyug

  1. 55 minutes ago, AdvancedSetup said:

    You're using an older version of the program. Please update the program and then scan again and let us know.

    No problem with 4.5.8

    However me using an older version should not have been an issue in this particular case since according to this thread the Telegram Uninstaller was whitelisted on Feb 21th and Malwarebytes 4.5.6 was released on March 15th (and I had no issue with it with daily scans).

    So not quite sure what happened here, anyway glad it is resolved.

    Thanks.

     

    3 minutes ago, cli said:

    Thanks for reporting this will be fixed in 10 minutes.

    While I was typing I saw this answer so ok, I guess something was off outside the version I used.

    Side question if I may,  in my log I can see "Rootkits: Disabled" but yet I have "Scan for Rootkits" turned on in the Malwarebytes UI, am I missing something ?

  2. 19 minutes ago, Porthos said:

    Please provide the log showing the detection.

    Malwarebytes

    www.malwarebytes.com

     

    -Log Details-

    Scan Date: 4/18/22

    Scan Time: 1:00 PM

    Log File: b0e46fec-bf06-11ec-b90f-00ff7704f40c.json

     

    -Software Information-

    Version: 4.5.6.180

    Components Version: 1.0.1634

    Update Package Version: 1.0.53847

    License: Premium

     

    -System Information-

    OS: Windows 10 (Build 19044.1645)

    CPU: x64

    File System: NTFS

    User: System

     

    -Scan Summary-

    Scan Type: Threat Scan

    Scan Initiated By: Scheduler

    Result: Completed

    Objects Scanned: 380098

    Threats Detected: 2

    Threats Quarantined: 0

    Time Elapsed: 7 min, 31 sec

     

    -Scan Options-

    Memory: Enabled

    Startup: Enabled

    Filesystem: Enabled

    Archives: Enabled

    Rootkits: Disabled

    Heuristics: Enabled

    PUP: Detect

    PUM: Detect

     

    -Scan Details-

    Process: 0

    (No malicious items detected)

     

    Module: 0

    (No malicious items detected)

     

    Registry Key: 1

    Malware.Sandbox.23, HKU\S-1-5-21-899963107-2307166598-3394742062-1001\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\UNINSTALL\{53F49750-6209-4FBF-9CA8-7A333C87D1ED}_is1, No Action By User, 23, 0, , , , , ,

     

    Registry Value: 0

    (No malicious items detected)

     

    Registry Data: 0

    (No malicious items detected)

     

    Data Stream: 0

    (No malicious items detected)

     

    Folder: 0

    (No malicious items detected)

     

    File: 1

    Malware.Sandbox.23, C:\USERS\***\APPDATA\ROAMING\TELEGRAM DESKTOP\UNINS000.EXE, No Action By User, 23, 0, 1.0.53847, 23, dds, 01732744, 637ED282D229E01FB1A01A3A6F2AC334, 2E94D37E28AE45BD6B099BE446C517BA7BC2067E0A21A6EE9BE464B030EBD5E9

     

    Physical Sector: 0

    (No malicious items detected)

     

    WMI: 0

    (No malicious items detected)

     

     

    (end)

  3. On 2/21/2022 at 5:22 PM, Porthos said:

    It was whitelisted because it was a False Positive so it would not be detected again.

    The very same thing happened to me today on Malwarebytes 4.5.6

    I did quarantine it anyway for peace of mind, thanks to clarify that it is once again a False Positive (not sure how it can happen if you did whitelist it).

    NB: So far I had the Telegram Uninstaller for years with no issue while doing daily Malwarebytes Scan.

  4. I'm not sure in which place I must put this discussion on the forum since I can't tell if I have indeed been hit by a real Malware or if it is a false positive.

    Just got the new Creators Update yesterday and today when I do run a Scan with Malwarebytes I got 9 hits with "Trojan.Agent.TskLnk" all linked to Windows SMB1 HKEY or files.

    Did a Quarantine and now system is clean.

    Side note: Zemana and Defender did not detect a thing.

    Question:

    1) Is it false or not ?

    2) If instead of Quarantine I delete the files, does that mean I can't use SMB1 anymore on my network ? (I got a ShieldTV that sadly needs SMB1 if I recall correctly)

     

    Malwarebytes report.txt

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.