STM32CubeIDE.exe detects as malware?

[MFran.9]

I have just installed STM32CubeIDE and started creating a project. I left shortly and found the application was closed on my return. The icon could no longer see the executable and just now it occurred to me that my security system detected it as a threat.

And in fact, it was detected as malware by BitDefender.

Is anyone else experiencing this?

[Tesla DeLorean]

ST's not responsible for what AV software chooses to do.

File a ticker with the BitDefender folks..

[MFran.9]

I was asking for others experience and not being offensive, so your welcome!!

But no... I exclude it from the scanned files. You can file it if you wish

[Pavel A.]

What is the malware/threat identifier in BitDefender?

[MFran.9]

It just detects it as "malicious behavior" and quarantines the exe file. I suspect it is when it starts to unzip the firmware pack.

[Nikita91]

Yes this happened to me too, with Avast. During installation the executable was quarantined silently.

Now I have enabled antivirus notifications, and I can intervene in time in the event of an alert.

[Markus GIRDLAND · Accepted solution]

I answered a similar issue in this thread but I can post it here as well:

We're aware that some software can get blocked by anti-virus, firewalls and companies' IT-departments so we always sign our software and try to make it as legitimate as possible as to not trigger any of these blockers.

At the end of the day we in the CubeIDE team try to bundle and sign everything as well as we can, but we can't control all the variables in the users environment so some cases like this might still pop up on the community.

[MFran.9]

Hi Markus,

As I mentioned already, it was not a complaint as I am well aware that these issues do come up in IDE's. It was to see if others experience the same and to indicate for others that it not uncommon.

I experienced it also from Microsoft Visual Studio, but the response there was rather hostile.

If there would be a place you want to investigate, maybe look at how the unpacking of firmware packages can bypass such detection and if that is even the problem.

Scanners are also getting more aggressive these days and does not make it easier on you guys :)