Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多
Open

I always get: "newmsg Trojan:WIN/SuspiciousAttachmentScript.a"

David Stanley replied
OfficePC

I always get: "newmsg Trojan:WIN/SuspiciousAttachmentScript.a" and "C:\Users\newb\AppData\Local\Temp Trojan:WIN/SuspiciousAttachmentScript.a" from Mcafee when I open Thunderbird. I'm only getting this in Thunderbird and suspect it's a false positive of some kind. It's still worrying and I'd like to eliminate this. This has been going on for a couple of months. I've run several cleaners and anti-virus programs on the system, but it still returns.

thanks

I always get: "newmsg Trojan:WIN/SuspiciousAttachmentScript.a" and "C:\Users\newb\AppData\Local\Temp Trojan:WIN/SuspiciousAttachmentScript.a" from Mcafee when I open Thunderbird. I'm only getting this in Thunderbird and suspect it's a false positive of some kind. It's still worrying and I'd like to eliminate this. This has been going on for a couple of months. I've run several cleaners and anti-virus programs on the system, but it still returns. thanks

所有回覆 (3)

Hi

Thunderbird temporarily extracts email attachments or scripts to your Windows AppData\Local\Temp folder and McAfee is watching that Temp folder and deletes that temporary file.

Do because the original email is still sitting in your Thunderbird inbox, the next time you open Thunderbird, it tries to sync and cache that email again and McAfee flags it again.

So you need to find that email end delete it from your Inbox/Junk/Spam folder

To find the exact email causing the issue, look at the McAfee history log, it might give you a specific file name.

Thanks for getting back. I'll try this.

I have had a similar problem in the last couple of days. The biggest issue was that I did not know where the newmsg file was coming from. I use the MS Defender antivirus which correctly deleted the file when it finds it is infected. Eventually I worked out it was from Thunderbird. I found a scanner from Emsisoft called Emergency Kit which was able to scan inside Thunderbird message stores and identify the problem messages. In my case they were more than 10 years old and buried in a folder.

What would have really helped is if the newmsg file was more helpfully named. Something like thunderbirdnewmsg would be so much better.

問個問題

如果您還沒有帳號,您必須先登入帳號 來回覆文章。還沒有帳號的話,只能發問新問題