Dylibs built on 1.78.0 <->1.87.0 gets flagged as trojans
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Code
Building dylibs from 1.78.0 stable and onwards creates .dlls that are flagged as trojans.
Tested on two different Windows 10 PCs with fresh installs.
1.78.0 cargo init dylib https://www.virustotal.com/gui/file/65e2ea31d0bc03ef70e3c342a7cddcabd22be2db5fd84dfbb4db18dd01e3c083/detection
1.77.0 cargo init dylib https://www.virustotal.com/gui/file/5b4fb7bfa7a13acc42f640bb4d6382cc820b499d010a64727326f006b23a4e46/detection
Version it worked on
It most recently worked on: 1.77.0
Version with regression
Anything past 1.77.0
I've looked here in the issues, forums, discord, google.. nada. I wonder how this hasn't been mentioned before?
This is quite annoying even though it is a false positive. My users are messaging me wondering why there is a trojan coming with the installation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by reproducing a dylib with cargo init dylib and comparing Rust 1.77.0 with 1.78.0 or later on Windows, then inspect the linked VirusTotal reports and the eight-comment thread. Done means identifying the change responsible for the false-positive trojan detections and confirming that affected dylibs are no longer flagged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100