Replies: 1 comment
-
Hi, sorry for the late reply. I see and can confirm this happens. You can try building it yourself and see if it still warns you about a trojan. The code is open-source. But anyway, to get to the point of the cause: I think it has to do with the fact that UAD-ng can execute ADB commands on a remote device (your phone) and is thus a false positive. There's nothing we can do about it, apart from reporting the tool to those virus scanners. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Virustotal scan report: https://www.virustotal.com/gui/file/eccdd8e05184388f2038e652afe3a77e1f6abc9d13e9fb21aad59cd6a924cb03
alternatively: https://hybrid-analysis.com/sample/eccdd8e05184388f2038e652afe3a77e1f6abc9d13e9fb21aad59cd6a924cb03/67e150258ba19fe9780a2825
I get that false positives happen, usually by a few virus/malware engines, but in this case half of them finding Trojan and puts very high threat score on the Windows version of UAD tool. If file is clean, what's causing it?
Beta Was this translation helpful? Give feedback.
All reactions