File scan report
Verdict Suspicious
Is Plutonium. Updater. App. exe safe? Treat it as suspicious.
The engine result alone is weak: 3 of 75 detections, none from major antivirus engines, and only one Quasar label.
Read the whole reasonShow less
Why Suspicious? 3 antivirus engines flag it, but no major engine agrees; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
If it came from a link, an attachment or a stranger, delete it.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't run it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already ran it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
3 of 70 flagged
- Flagged 3
- No detection 67
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 3y ago
Chapter 02
Why we think so
5 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Three of the 70 antivirus engines that checked it flagged the sample, with no major detections or family consensus, so the Quasar identification is not established. The executable is unsigned and appears packed, and ten researcher YARA rules matched it, adding meaningful static corroboration. Its age, broad prevalence, lack of a malicious sandbox verdict, and absence of confirmed malicious files it created reduce certainty. Host-reputation coverage was incomplete because only one host was inspected despite numerous observed IP and URL contacts.
What We Detected
Three of the 70 antivirus engines that checked it flagged the executable. MaxSecure and VBA32 supplied generic MSIL-trojan labels, while Zillya named Quasar; no major antivirus engines agreed, so the family attribution remains unconfirmed. The file is unsigned, and its code section has entropy 8 with peAnalysis.likelyPacked=true.
Threat Behavior
One completed sandbox run recorded six offensive mappings: T1055, T1485, T1486, T1547.001, T1562.001, and T1620. The program downloaded multiple components from its update infrastructure, while ten community YARA rules matched the sample. No malicious sandbox verdict or confirmed malicious child was recorded, but all ten inspected children remain unclassified. Only one contacted host received a reputation lookup, so the numerous observed IP and URL contacts were not comprehensively checked.
What To Do Now
Do not execute this copy on a production or personal system until its SHA-256 is independently matched against the official publisher’s release.
Where this verdict could be wrong5 caveats
- Sixteen major antivirus engines, including BitDefender, Kaspersky, ESET-NOD32, and Microsoft-class peers represented in tier1ReportedClean, did not flag the sample; no major family consensus exists.
- No dropped file is known to be malicious, but all 10 children retained unknown verdicts, so this does not establish that the downloaded components are benign.
- No sandbox returned a malicious verdict, despite the recorded offensive-technique mappings.
- The file is old and widely submitted: it was submitted 35788 times and it has 3723 distinct submitters.
- contactedHosts.inspected=1 does not cover the many distinct behaviour.contactedIps and contactedUrls, so host reputation remains incomplete.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 3/70 engines detected the sample
- No major antivirus engines flagged it and 16 major antivirus engines reported it clean
- No sandbox returned a malicious verdict
- No dropped file is known to be malicious
- 35788 submissions across 3723 sources since 2023
- Unsigned Win32 executable
- Packed or obfuscated code with .text entropy of 8
- Runtime mapping to process injection
- Ten YARAify rule matches
- Incomplete reputation coverage for observed network contacts
6 sources checked · 5 complete · 1 partial. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 30sandbox rule tags
- 5spawned processes
- 8network contacts
- 40filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Checked whether it was running on a test computer.
Note: Listed the programs running on the test computer.
Note: Deleted files or logs during the test run (installers often clean up after themselves).
Note: Talked to servers over the internet during the test run.
Note: Read basic details of the test computer, such as its Windows version.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as recording keystrokes; no keylogging was confirmed.
Not confirmed: Showed activity a sandbox rule links to file encryption; no ransomware behaviour was confirmed.
Not confirmed: A sandbox rule tagged this run as setting up auto-start; no auto-start entry was recorded.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 7: FileSeen in the test run
Plutonium.Updater.App.exe
85d1d1ca4d5881d9b98928c2006fb0eec9655e2705fe74088e6f974a19703f0f
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
program.exe
"C:\Users\<USER>\Desktop\program.exe"
Test run - Evidence 3 of 7: ProcessSeen in the test run
6758f19f-a372-418e-9272-f2fbdf24ab20.exe
"C:\Users\<USER>\AppData\Local\Temp\6758f19f-a372-418e-9272-f2fbdf24ab20.exe" /Q
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
AppCore.dll
C:\Users\<USER>\AppData\Local\Plutonium\bin\AppCore.dll
Test run - Evidence 5 of 7: Written fileSeen in the test run
Ultralight.dll
C:\Users\<USER>\AppData\Local\Plutonium\bin\Ultralight.dll
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
172.67.71.109
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
104.21.96.35
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes 30 mapped techniques, every process, file, registry and network entry and 9 dropped files.
Show the technical evidenceChapter 04
Technical details
3 of the 70 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 3
- MaxSecureTrojan.Malware.300983.susgen
- VBA32TScope.Trojan.MSIL
- ZillyaTrojan.Quasar.Win32.7348
File fingerprint
- Last analyzed
- Sep 10, 2026, 9:30 PM UTC
- SHA-256
85d1d1ca4d5881d9b98928c2006fb0eec9655e2705fe74088e6f974a19703f0f- SHA-1
8681469349254c5203a7f9a189833d22a14f5cd9- MD5
72cb7c6d98e9e47274733825c9176679
About this file
Plutonium.Updater.App.exe is a Win32 EXE file of 4.9 MB.
- Type and size
- Win32 EXE · 4.9 MB
- Signer
- UnsignedNo code signature.
- First seen
- Feb 23, 2023On VirusTotal.
- Submitted by
- 3,723 distinct sources
- Packer
- None detected
- Entropy
- 7.64 of 8
First scanned Updated
Includes every engine result (75), 11 matched signature rules, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 7 questions people ask most about this file.
Is Plutonium.Updater.App.exe safe, or is it malware?
What is Plutonium.Updater.App.exe?
How many antivirus engines detected Plutonium.Updater.App.exe?
What should I do if I already ran Plutonium.Updater.App.exe?
Is Plutonium.Updater.App.exe digitally signed?
What is the SHA-256 hash of Plutonium.Updater.App.exe?
How up to date is this analysis of Plutonium.Updater.App.exe?
Community
Member reviews and reports for this exact file hash.