Telegram.Bot.dll PUA classification with ESET problem

[bestByteCode]

Hi,

I recently encountered an issue where the Telegram.Bot.dll is being flagged as a Potential Unwanted Application (PUA) by ESET's security software. This flagging may affect the user experience and trust in the Telegram.Bot library.

You can see details here. https://www.virustotal.com/gui/file/e1238a1eb84e0b3f3ed3a7bcc01c90aeec44fa8f1790d02aa1b6cad5383c295e

Could you please look into this matter? It might involve reaching out to ESET for clarification or resolving any security concerns that led to this classification. Your attention to this issue would be greatly appreciated, as it could help ensure the library remains a trusted tool for developers.

[tuscen]

@bestByteCode Thanks for your report. I've sent an email to ESET.

[bestByteCode]

@tuscen Do you have any update on this? We're still blocked this.

[tuscen]

Still no answer from ESET, unfortunately. I guess public backlash on social media can push this further like it always does with large companies, but I don't have many followers on social media profiles

[fbhp]

Have the same problem with Bitdefender and Telegram.Bot.dll

[tuscen]

There's still not much progress, unfortunately. We're working with the Nuget team to find a solution

[keksikq09]

Have the same promlem , using .net library for tg bots

[bairog]

@tuscen Is there any progress from ESET or Nuget team side?

[tuscen]

@bairog No, the issue is still not resolved and we don't know when it will be resolved.

[bairog]

@tuscen Do I understand correctly that nugets from alternative feed (https://nuget.voids.site/packages/Telegram.Bot) supports latest API but can be classified as malware by ESET/Bitdefender/etc?

[tuscen]

@bairog yes, correct. This feed is currently our main one. I'm trying to create a separate public azure feed for release packages to replace it

[bairog]

I'm trying to create a separate public azure feed for release packages to replace it

But that will not solve the problem of antiviruses false positives. Ok, now I better understand the current situation, thank you.

[wiz0u]

No need to keep this issue opened. We're still working on resolving this issue of course, you'll be all informed once PUA classification has been lifted.

See also pinned issue #1375