You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Security issue reported by my antivirus (Bitdefender) #67246
You must restart your device to finalize the cleaning process.
Bitdefender detected potentially malicious behavior and blocked all applications involved.
Detection ID: SuspiciousBehavior.D4BFD735138DA7EE
Closing this issue, as it is not actionable by Node.js.
You may be able to get help from https://community.bitdefender.com/en/. There is also a comment here in the issue list #33284 that other users needed to add exceptions in Bitdefender.
Desktop virus protection programs can produce false positives on Node.js and installed dependencies.
If you have any other concrete information that something needs to be changed in Node.js, then please respond and we can re-open the issue.
Activity
Mohammadtrabelsi commentedon Nov 4, 2026
MikeMcC399 commentedon Nov 4, 2026
It appears that you are receiving a warning from a third-party virus protection product Bitdefender running on Windows.
The screenshot that you posted does not identify any specific vulnerability. It is also showing vite, which is another dependency.
You may be able to get support from Bitdefender to identify the exact cause and to find out if there is any workaround.
[-]Security issue reported by my antivirus[/-][+]Security issue reported by my antivirus (Bitdefender)[/+]MikeMcC399 commentedon Nov 4, 2026
Closing this issue, as it is not actionable by Node.js.
You may be able to get help from https://community.bitdefender.com/en/. There is also a comment here in the issue list #33284 that other users needed to add exceptions in Bitdefender.
Desktop virus protection programs can produce false positives on Node.js and installed dependencies.
If you have any other concrete information that something needs to be changed in Node.js, then please respond and we can re-open the issue.