Downloading the regular Rufus executable (which I regularly use on my computer) did not produce such a notification. Of course, that's not the portable version, which I'm fully aware of.
The publisher appears to have rebuilt the app and re-released it with a new digital signature on June 23 but kept the same version number. That's why if you download it now it doesn't have the same SHA256 and shows clean. I'm packaging that now as 3.1 Build 2.
UPDATE: 3.1 Build 2 has been posted.
UPDATE (2018-06-26): Microsoft has fixed their false positive issue with the original 3.1 build.
Sometimes, the impossible can become possible, if you're awesome!
Please help support us by making a donation so we can keep bringing you awesome free software. We accept credit card, wire transfer, PayPal, cryptocurrency, and more.
Here's VirusTotal's findings -> https://www.virustotal.com/#/file/47de4987c3e6f96f7d4898aa5aabf26bcf2d9c...
I also received notice that the executable was infected after updating my PortableApps this morning...
Downloading the regular Rufus executable (which I regularly use on my computer) did not produce such a notification. Of course, that's not the portable version, which I'm fully aware of.
There appears to be a false positive in Rufus within the Microsoft and Ikarus engines. You can see a scan of rufusp.exe/rufus-3.1.exe here:
https://www.virustotal.com/#/file/a81cba62d55ee42f41303c138a439d5dc42075...
And an updated scan of the Rufus Portable package here:
https://www.virustotal.com/#/file/47de4987c3e6f96f7d4898aa5aabf26bcf2d9c...
The publisher appears to have rebuilt the app and re-released it with a new digital signature on June 23 but kept the same version number. That's why if you download it now it doesn't have the same SHA256 and shows clean. I'm packaging that now as 3.1 Build 2.
UPDATE: 3.1 Build 2 has been posted.
UPDATE (2018-06-26): Microsoft has fixed their false positive issue with the original 3.1 build.
Sometimes, the impossible can become possible, if you're awesome!