New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows Defender identifies binary as trojan #1

conioh opened this Issue Jun 23, 2016 · 4 comments


3 participants

conioh commented Jun 23, 2016

Identified as: Win32/Spallowz.A!cl

Category: Trojan

Description: This program is dangerous and executes commands from an attacker.

Recommended action: Remove this software immediately.

file:C:\ProgramData\Microsoft\Windows Defender\Scans\FilesStash\260A5552-CCD4-7324-ECB2-4F4BC7C2A253_1d1ce1b1363ccb0
webfile:C:\ProgramData\Microsoft\Windows Defender\LocalCopy{9D978906-6B4F-4B93-8A83-89B5389F0367}-260A5552-CCD4-7324-ECB2-4F4BC7C2A253_1d1ce1b1363ccb0|chrome.exe
webfile:C:\ProgramData\Microsoft\Windows Defender\Scans\FilesStash\260A5552-CCD4-7324-ECB2-4F4BC7C2A253_1d1ce1b1363ccb0||chrome.exe

Get more information about this item online.


This comment has been minimized.


hfiref0x commented Jun 23, 2016

Microsoft problem. I will not waste my time contacting any AV regarding their schizophrenic detections and will not do anything to "bypass" this detect. This project is open source. If you have any doubts about it, look inside, nothing is hidden.

in memory detect fp.

@hfiref0x hfiref0x closed this Jun 23, 2016

@hfiref0x hfiref0x reopened this Nov 30, 2017


This comment has been minimized.

TPS commented May 20, 2018

The zip of today's binary passes just fine.:

I suppose that means the binary inside should be OK, too.


This comment has been minimized.

@hfiref0x hfiref0x closed this May 20, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment