File scan report

Verdict Suspicious

Analyzed , 1 month ago

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.

Don't run it until you know where it came from

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

  1. Don't run it unless you're sure where it came from.

  2. Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.

  3. 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

  1. 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.

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
FilePlutonium.Updater.App.exe4.9 MBSHA-256 85d1d1ca4d58…703f0f
  • Code signing Unsigned
  • Test run Completed
  • First seen 3y ago
3 of the 70 antivirus engines that checked it flag it, including Zillya and MaxSecure.

Chapter 02

Why we think so

5 points against it and 5 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

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.

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.

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.

Seen in the test runWorked out from other results
  1. Input file

    The submitted object

    1
    1. Evidence 1 of 7: FileSeen in the test run

      Plutonium.Updater.App.exe

      85d1d1ca4d5881d9b98928c2006fb0eec9655e2705fe74088e6f974a19703f0f

      Uploaded file
  2. Processes

    What ran

    2
    1. Evidence 2 of 7: ProcessSeen in the test run

      program.exe

      "C:\Users\<USER>\Desktop\program.exe"

      Test run
    2. 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
    3. +1 more recorded observation
  3. Files

    Created or changed

    2
    1. Evidence 4 of 7: Written fileSeen in the test run

      AppCore.dll

      C:\Users\<USER>\AppData\Local\Plutonium\bin\AppCore.dll

      Test run
    2. Evidence 5 of 7: Written fileSeen in the test run

      Ultralight.dll

      C:\Users\<USER>\AppData\Local\Plutonium\bin\Ultralight.dll

      Test run
    3. +1 more recorded observation
  4. Network

    Hosts contacted

    2
    1. Evidence 6 of 7: Contacted hostSeen in the test run

      172.67.71.109

      Contacted during the test run.

      Test run
    2. Evidence 7 of 7: Contacted hostSeen in the test run

      104.21.96.35

      Contacted during the test run.

      Test run
    3. +1 more recorded observation

7 facts from the test run. See the full activity list.

Chapter 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.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteRisk signal: 3 of 70 engines flagged it · 5 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteRuntime behaviour was recorded Details for sandbox run
Contacted hostsMalwareTips URL scannerPartial1 of 17 contacted hosts were cross-checked; coverage is incomplete Details for contacted hosts
Signature rulesYARAify community rules + MalwareTips rulesComplete10 community YARA rules · 1 MalwareTips behaviour rule Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

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

Chapter 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?
Plutonium.Updater.App.exe is rated Suspicious: some signs point to a problem, but nothing confirms it is harmful. 3 of the 70 antivirus engines that checked it flag it. Don't run it unless you're sure where it came from. If you need the program, download it again from the publisher's own website.
What is Plutonium.Updater.App.exe?
Plutonium.Updater.App.exe is a Windows program, about 4.9 MB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Feb 23, 2023.
How many antivirus engines detected Plutonium.Updater.App.exe?
3 of the 70 antivirus engines that checked it flag Plutonium.Updater.App.exe, including Zillya and MaxSecure. We weigh which engines flagged it and what else the scan found, not just the count.
What should I do if I already ran Plutonium.Updater.App.exe?
No infection is confirmed: the rating is a caution, not a malware finding. 1) Check where it came from. If you can't confirm the source, delete it. 2) Run a full scan with your security software. 3) If the scan finds something, follow its removal steps and change passwords you typed on the device since then.
Is Plutonium.Updater.App.exe digitally signed?
No. Plutonium.Updater.App.exe is not digitally signed. Many legitimate files aren't either, but it means nothing proves who published it.
What is the SHA-256 hash of Plutonium.Updater.App.exe?
The SHA-256 fingerprint of Plutonium.Updater.App.exe is 85d1d1ca4d5881d9b98928c2006fb0eec9655e2705fe74088e6f974a19703f0f, and its MD5 is 72cb7c6d98e9e47274733825c9176679. Two files with the same SHA-256 are identical, so use it to check you have exactly this file, not just one with the same name.
How up to date is this analysis of Plutonium.Updater.App.exe?
This report reflects the scan on Sep 10, 2026. A file's fingerprint never changes, but antivirus engines keep learning, so a rating can change later. To get a newer result, scan the file again: we refresh the antivirus results when the saved ones are out of date.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Recent reports on other files with the same rating.

All file reports
This report and its SHA-256 fingerprint are public, so the next person who checks the same file gets an instant answer; documents and images are listed by type instead of their file name. A file we had not seen before is uploaded to VirusTotal, whose security partners and subscribers can download it; MalwareTips deletes its own copy after the scan. If you ran this file and are worried, scan your device with up-to-date security software.