-
Notifications
You must be signed in to change notification settings - Fork 720
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
React-Three_drei.js flags as malware only on Avast Antivirus #2239
Comments
Confirmed here too , with "@react-three/drei": "^9.117.3". |
Hi. I also get the same ERROR. It is with the DREI and LEVA libraries in Three.js. Do you know if this library can harm my PC? Thanks |
Same Here... Is it ok to continue using @react-three/drei ..? |
Looking through Avast's write up on it they give little to no details. It looks like It's common to false flag libraries too which makes it hard to chase down. Are you using and PDF software or you site? Can you try any of the sandbox pages of this repo and see if they fire? If they don't, it's probably something else in your project getting dinged. |
in my case online Sandboxes work well i think is only relative to the compiled version of drei if i import drei in my App like
a file @react-threee_drei_DATE_.js is generated and |
can you provide a link to one? |
three
version: 0.164.1@react-three/fiber
version: 8.16.8@react-three/drei
version: 9.107.0node
version: 20.12.2npm
(oryarn
) version: 10.6.0Problem description:
The dependency @react-three_drei.js is false flagged as a Trojan Horse virus by Avast, specifically a "JS:Prontexi-Z [Trj]" threat. I'm unsure what part of the library is being flagged.
Relevant code:
Part of the problem is that I can't track down which snippet of drei is flagging Avast's database. So I'm unable to provide relevant code.
Suggested solution:
If someone who would know how to identify what JS:Prontexi-Z is and find it within @react-three_drei, either it could be removed or updated to not be automatically flagged as a Trojan Horse virus.
Obviously this is only a problem with Avast, maybe a representative of Poimandres could reach out to Avast to get them to update their own database.
The text was updated successfully, but these errors were encountered: