Skip to content
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

Virus Warning with DryIoc Version 5.4.3 on Some Antivirus Software #650

Open
raymond-liao opened this issue Jun 25, 2024 · 1 comment
Open

Comments

@raymond-liao
Copy link

Description

We encountered an issue where our antivirus software flagged the DryIoc package version 5.4.3 as containing a virus (VirTool.MSIL.Obfuscator.f281). This warning appears when the package is installed via NuGet. However, using the DryIoc.dll directly from the same version does not trigger the antivirus warning.

image

Steps to Reproduce

  1. Install DryIoc version 5.4.3 via NuGet.
  2. Compile the project.
  3. Observe the antivirus software warning about VirTool.MSIL.Obfuscator.f281.

Expected Behavior

No antivirus warnings should be triggered when using the DryIoc package.

Actual Behavior

Antivirus software flags DryIoc package version 5.4.3 as containing a virus.

Workaround

Using DryIoc.dll directly from the same version (5.4.3) does not trigger the antivirus warning.

Environment

  • DryIoc version: 5.4.3
  • .NET version: [Your .NET Version]
  • Antivirus software: [Your Antivirus Software]

Antivirus Software Details

  1. QiAnXin TianQing (奇安信天擎):
  2. Huorong Security (火绒安全):

These antivirus software packages can be used to verify and potentially resolve the issue.

Additional Information

This issue might affect other users, so it would be beneficial to investigate and resolve the root cause. We wanted to inform you about this and share our workaround. Please let us know if any further information or assistance is required.

Thank you for your work on DryIoc!

@dadhi
Copy link
Owner

dadhi commented Jun 25, 2024

@raymond-liao Hi, interesting issue.
I am not sure what causing the issue. Probably something inside the package bundle.
Could you check if the same happens for the latest 6.0.0-preview-07 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants