“Dear Mr. Monero, Thank you for your request. We have reviewed the reasons of the automatic block action by AdminByRequest, and it’s due to the file containing a Trojan (Trojan/Malware!2pCjDQTN). This can be related to not using trusted downloading sources. In this case it’s a OpenSource software with no guarantee, nor support. It’s strongly discouraged to avoid downloading software from non-validated sources. If this software is so business important, we would encourage you to contact the Product Owner of Autodesk/AutoCAD to consider this demand and source adequate software packages to accomplish the required tasks.”
Now, I have used pyrevit for years, but I cannot in my new computer, and this is slowing a lot my work
Can they provide further information on the nature of the file and how it was detected? E.g. is it bundled in with the dll or in a particular location of the installed files.
Sometimes some AV software sees files as malware that may not actually be true malware.
…somewhat related. Our IT imposed another security protocol over the weekend. We walked in and all 2023 projects on the cloud failed. This protocol is in ADSK 2024 and 2025, but not 2023.
Our only option is to upgrade everything to 2024 or beyond. Now we have a 2023 casino in construction with released drawings and we have to upgrade the project. A lot of data. A lot of files. And we have to ensure 100% drawing fidelity. That’s going to be massive man hours.
Antivirus/anti-threat programs using heuristic can sometimes report false positives, and most of them don’t tollerate dlls and exe files without the signature; Windows Defender Smart Screen will complain about and block unsigned programs;
signing the files is not free, and most of the small, open-source programs cannot afford to sign their releases
until pyRevit 4.x, all the dlls and executables (installer included) have been signed using a certificate that Ehsan bought a while ago, but unfortunately we’re past its expiration date.
@Jean-Marc did the tremendous job of finding the right solution to keep signing the files without having to sell a kidney
unfortunately, the pipeline for the 5.0.0 release wasn’t set up correctly, so the installer was signed, but the dlls in it were not. That’s why AdminByRequest treated pyrevit as a threat
This was fixed by the release of pyRevit 5.0.1, so you can safely use this version in your corporate environment (then use pyrevit to run python to send a real trojan to your IT )
BTW: I won’t trust a security company that sponsors the slowest F1 team of the last year