MalwareTips

File scan report

Scan another file

Verdict Suspicious

Analyzed , 1 month ago

Is dlssnr_on_amd_setup.exe safe? Treat it as suspicious.

Six of the 71 antivirus engines that checked it flagged the file, including one major antivirus engine.

Why Suspicious? 6 antivirus engines flag it; nothing else confirms it.

Limited evidence · One sign points to a problem; nothing else confirms it.

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

Treat the file as suspicious; avoid execution until further vendor detections or sandbox corroboration appear.

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 install 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 installed 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.

Why we think so

Share this file report

dlssnr_on_amd_setup.exe: Suspicious — MalwareTips file scan

The link always shows the latest result for this exact file (its SHA-256 fingerprint).

Reads the latest antivirus results for this file's hash. Nothing is uploaded.

Antivirus results

6 of 71 flagged

  • Flagged 6
  • No detection 65
  • No result 4
Filedlssnr_on_amd_setup.exe7.4 MBSHA-256 66b910da005e…438092
  • Code signing Unsigned
  • Test run Completed
  • First seen 1mo ago
6 of the 71 antivirus engines that checked it flag it, including Symantec (Norton) and CrowdStrike.

Chapter 02

Why we think so

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

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

The one detection from a major antivirus engine is a generic ML attribute label rather than a named family, limiting confidence. Unsigned status removes any signer-history reassurance. Offensive MITRE techniques observed in the sandbox plus access to the Windows password store raise concern, but medium prevalence and lack of files it created or malicious host contacts keep the file from crossing into a clear malicious verdict.

6 sources checked · 5 complete · 1 not needed or not applicable. 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
  • 13sandbox rule tags
  • 2spawned processes
  • 0network contacts
  • 18filesystem & 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: Checked whether it was running on a test computer.

  • Note: Read the user name of the test computer.

  • Note: Read basic details of the test computer, such as its Windows version.

  • Note: Looked through folders on the test computer (most installers do this).

  • Note: Loaded extra code modules while running.

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: A sandbox rule tagged this run as contacting a server, but no contacted host was recorded.

  • Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.

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 5: FileSeen in the test run

      dlssnr_on_amd_setup.exe

      66b910da005e000070256b55c41dd5d0e1ae1ea6a8c3a9d0b76edc1749438092

      Uploaded file

  2. Processes

    What ran

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

      dlssnr_on_amd_setup.exe

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

      Test run
    2. Evidence 3 of 5: ProcessSeen in the test run

      dlssnr_on_amd_setup.exe

      "C:\Users\user\Desktop\dlssnr_on_amd_setup.exe"

      Test run
    3. +1 more recorded observation

  3. Files

    Created or changed

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

      New folder

      C:\Users\<USER>\Pictures\New folder

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

      Caches

      C:\Users\user\AppData\Local\Microsoft\Windows\Caches

      Test run
    3. +1 more recorded observation

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

Chapter 04

Technical details

6 of the 71 antivirus engines that checked it flag it; no publisher signature.

Sources checked

Every check behind this verdict

6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteRisk signal: 6 of 71 engines flagged it · 4 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteRuntime behaviour was recorded Details for sandbox run
Contacted hostsMalwareTips URL scannerNot neededThe sandbox recorded no contacted hosts to checkNo date recorded
Signature rulesYARAify community rules + MalwareTips rulesComplete1 MalwareTips behaviour rule Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

Engines that flagged it 6

  • Symantec (major engine)ML.Attribute.HighConfidence
  • APEXMalicious
  • BkavW32.Malware.FDA5CBBB
  • CrowdStrikewin/malicious_confidence_70% (W)
  • Elasticmalicious (moderate confidence)
  • Trapminesuspicious.low.ml.score

File fingerprint

Last analyzed
Sep 8, 2026, 1:20 AM UTC
SHA-256
66b910da005e000070256b55c41dd5d0e1ae1ea6a8c3a9d0b76edc1749438092
SHA-1
4bce07705d68163524af753ec51308737c6391bb
MD5
4fb4bc9064606ea20aaeaa4752d54f75

About this file

dlssnr_on_amd_setup.exe is a Win32 EXE file of 7.4 MB.

Type and size
Win32 EXE · 7.4 MB
Signer
UnsignedNo code signature.
First seen
Sep 5, 2026On VirusTotal.
Submitted by
79 distinct sources
Packer
None detected
Entropy
6.41 of 8

First scanned

Chapter 05

Questions & answers

Short answers to the 6 questions people ask most about this file.

Is dlssnr_on_amd_setup.exe safe, or is it malware?
dlssnr_on_amd_setup.exe is rated Suspicious: some signs point to a problem, but nothing confirms it is harmful. 6 of the 71 antivirus engines that checked it flag it. Don't install it unless you're sure where it came from. If you need the software, download a fresh installer from the developer's own website.
What is dlssnr_on_amd_setup.exe?
dlssnr_on_amd_setup.exe is a software installer, about 7.4 MB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Sep 5, 2026.
How many antivirus engines detected dlssnr_on_amd_setup.exe?
6 of the 71 antivirus engines that checked it flag dlssnr_on_amd_setup.exe, including Symantec (Norton) and CrowdStrike. We weigh which engines flagged it and what else the scan found, not just the count.
What should I do if I already installed dlssnr_on_amd_setup.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.
What is the SHA-256 hash of dlssnr_on_amd_setup.exe?
The SHA-256 fingerprint of dlssnr_on_amd_setup.exe is 66b910da005e000070256b55c41dd5d0e1ae1ea6a8c3a9d0b76edc1749438092, and its MD5 is 4fb4bc9064606ea20aaeaa4752d54f75. 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 dlssnr_on_amd_setup.exe?
This report reflects the scan on Sep 8, 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.

Related file reports

Recent reports on other files with the same rating.

All file reports
Scan another
Check a different file
URL instead?
Check if a link is safe
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.