Jump to content

False Positive - SAPIEN PowerShell Studio Exe Packager


ALIENQuake

Recommended Posts

Log for staff.

Malwarebytes
www.malwarebytes.com

-Log Details-
Scan Date: 5/3/21
Scan Time: 9:29 AM
Log File: ff6f384e-ac1b-11eb-b937-001a7dda7102.json

-Software Information-
Version: 4.3.3.116
Components Version: 1.0.1289
Update Package Version: 1.0.40105
License: Premium

-System Information-
OS: Windows 10 (Build 19042.964)
CPU: x64
File System: NTFS
User: I7-PC\SAPC

-Scan Summary-
Scan Type: Custom Scan
Scan Initiated By: Manual
Result: Completed
Objects Scanned: 1
Threats Detected: 1
Threats Quarantined: 0
Time Elapsed: 0 min, 7 sec

-Scan Options-
Memory: Disabled
Startup: Disabled
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: 0
(No malicious items detected)

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.AI.4237891851, C:\MALWARE TEST\PROJECTINFINITY\PROJECTINFINITY.EXE, No Action By User, 1000000, 0, 1.0.40105, BB4B4F528E00F972FC99190B, dds, 01229063, 81201D3F677859DB44B73281584D229B, 47A28C74F15F4305FF6C8A6CCF269D80BF21F540184BB26F1986D8FCDCA59F48

Physical Sector: 0
(No malicious items detected)

WMI: 0
(No malicious items detected)


(end)

Link to post
Share on other sites

2 hours ago, ALIENQuake said:

I've run re-detection (2021-05-04 21:22:45 UTC) and I'm still getting the same detection.

The engine format and configuration in VirusTotal is different than the consumer and corporate products’ default configuration. In VirusTotal Malwarebytes uses a command-line engine with different configuration and detection techniques/heuristics which might detect more than the commercial product. There are also false-positive suppression mechanisms in the commercial product which are not present in the command-line engine in VirusTotal.

This will eventually fix itself in Virustotal as well, as Malwarebytes has no control over this. Virus Total is having trouble reaching Malwarebytes cloud.

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.