Skip to content
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

Virus at esptool-0.4.9-win32.zip? #44

Open
burner- opened this issue Oct 15, 2016 · 5 comments
Open

Virus at esptool-0.4.9-win32.zip? #44

burner- opened this issue Oct 15, 2016 · 5 comments

Comments

@burner-
Copy link

burner- commented Oct 15, 2016

Suddenly F-Secure remove esptool.exe
I download https://github.com/igrr/esptool-ck/releases/download/0.4.9/esptool-0.4.9-win32.zip and unzip it and it remove also that.
I upload exptool.exe to virustotal and result looks quite alarming https://www.virustotal.com/en/file/3b6691658dc47298f784a89321866e5519498fdc015aea27f9ad237667e799ab/analysis/1476526377/
8 / 46 virus scanners detect is as troijan. Is is compiled with infected machine?

@igrr
Copy link
Owner

igrr commented Oct 16, 2016

Releases are built on Appveyor, that's an automated build in a container. Then it is directly uploaded to GitHub. Honestly, I have no idea where to start looking for a potential source of infection...

@burner-
Copy link
Author

burner- commented Oct 16, 2016

Most probably it is then false positive. I sent that file to F-Secure. Hopefully they will can give more information why it is detected as troijan.

@burner-
Copy link
Author

burner- commented Oct 16, 2016

I got answer from F-Secure. They say that it is false positive and they will make update to db soon.

@davidparreira
Copy link

Cisco and its Advanced Malware Protection (AMP) product is also detecting it as malware... Unfortunately, you need a contract with Cisco to report it as a false positive.

@sluzynsk
Copy link

I work for Cisco and I'll try to report it into that team.

I did an in-depth analysis with Cisco ThreatGrid and there are two reasons it is triggering as malware:
1 - the COFF header timestamp is set incorrectly - the compiler or linker isn't setting it to a current date
2- there are callback functions in thread local storage, which is apparently a technique malware uses to execute code prior to the debugger can attach to the process.

The second item is the larger issue in terms of why it is seen as malware.

I don't know that you have any control over either of those issues via build options, but that's why it's triggering.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants