-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
v2.13.23 is flagged to have a Trojan FVTV by MacAffee #8219
Comments
I also started getting alerts today from McAfee VirusScan for Linux. It started with dat_set_version 10852.
|
Thanks for the report, this is something we are looking into further. If anyone else has related info to share on this please let us know here. |
At this time, we believe this is a false positive. However, in order to confirm it is a false positive and clear the detections, we'll need to submit reports to the AV vendors flagging the executables. We are currently working on this and will keep this issue updated. |
Hello, on my side, McAfee started to detect aws and aws_completer as a trojan on Tuesday 3rd (it was OK on Monday), I believe with DATv3 5303. I'm not sure which version I have, probably 2.13.23. |
Same issue using versions 2.13.13, 2.11.7 and 2.11.21. Our Linux AV is from Fortra and uses Trellix (McAfee) for AV definitions which are updated automatically every night. |
Same issue Trellix and aws-cli v2.12.7 |
Trellix has tested files I sent against today's 10854 definitions and do not get the alert, the definition stack I had that did was 10853 |
I just got no alerts on a scan that was alerting yesterday. Anyone else experiencing clean scans now? Do we know if the definitions have been updated/corrected? |
I'm getting clean scans now with updated definitions after restoring the deleted files |
Also clean on my side for aws-cli 2.13.24 and with DAT v3 5305. |
I do not get any Trojan alerts anymore for the version 2.13.24 via WIZ (and thus VirusTotal) anymore. So @tim-finnigan - at least from my view, this ticket can be closed? |
That's odd, because I keep getting alerts for 2.13.24 - SHA256:c140d048f350d70ccdbb10ed5a4f152ad168aca8b586bddd10d94d93abc0497c |
Thanks all for reaching out regarding the scan report flagging issues with AWS CLI v2. We are actively working with the virus scanning vendors to investigate the detections. We have not identified any impact and are working to confirm this is a false positive. |
It appears that TrendMicro and McAfee are no longer flagging the CLI and we have not received any other reports here. I'll go ahead and close this issue but if anyone is still seeing the CLI flagged in any scans please share those details with us. |
|
Describe the bug
The current version v2.13.23 has been flagged by McAffee as containing a trojan, thus causing critical alerts in our monitoring infrastructure:
https://www.virustotal.com/gui/file/a2d89814f1fe981dce1721d07a52f01f9004d457a7d502211154732df0a9da54/detection
Which is most probably a false positive? (As no other scanners are reporting this)
Expected Behavior
No suspicious findings in malware scanners.
Current Behavior
MacAffee finding: Trojan-FVTV!4139E39A3B8C
Reproduction Steps
Scan the binary with MacAffee?
Possible Solution
No response
Additional Information/Context
CLI version used
v2.13.23
Environment details (OS name and version, etc.)
Ubuntu Jammy20230816
The text was updated successfully, but these errors were encountered: