MalwareTips

File scan report

Scan another file

Verdict Malicious

Analyzed , 1 month ago

Is AdskNLM.exe safe? No, we rate this exact file malicious.

Unsigned Autodesk licensing crack flagged by 43 of the 71 antivirus engines that checked it, including 12 major antivirus engines labelling it a cracking tool, and it drops a…

Read the whole reasonShow less

Strong evidence · Two or more major antivirus engines agree.

Don't run this file

Delete this file and run a full scan with your security software enabled; use only officially licensed Autodesk software.

What to do now5 steps

This file is harmful. Don't run it, and remove it.

If you haven't run it

  1. Don't run this file. Delete it, then empty the Recycle Bin.

If you already ran it

  1. Disconnect the device from the internet, then run a full antivirus scan. Microsoft Defender Offline (Windows Security > Virus & threat protection > Scan options) also finds malware that hides while Windows runs.

  2. If you typed passwords on the device after running it, change them from another device you trust.

  3. It created a file that antivirus engines classify as malicious, so run a full scan, not a quick one.

  4. If the scan keeps finding it, or the device still acts strangely, scan again with a second-opinion scanner from another company; if that doesn't fix it, back up your personal files and reinstall Windows.

If you already ran it, do these in order.

If you opened or installed it

Avoid banking and sign-ins on that device until it is clean. These free MalwareTips guides walk you through it.

Paste this report's link in your topic so helpers can see what was found.

Why we think so

Share this file report

AdskNLM.exe: Malicious — 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

43 of 71 flagged

  • Flagged 43
  • No detection 28
  • No result 4
FileAdskNLM.exe7.8 MBSHA-256 387afcf32a29…7cfb3b
  • Code signing Unsigned
  • Test run Completed
  • First seen 1y ago
It created a file that antivirus engines classify as malicious.

Chapter 02

Why we think so

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

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

43 of the 71 antivirus engines that checked it flag this file, with ESET, Ikarus, Fortinet and others naming it a software crack and Microsoft and TrendMicro labelling it a trojan. In testing it dropped licence-bypass components and a known-malicious file, removed an Autodesk startup entry and launched a randomly named program.

Where this verdict could be wrong1 caveat
  • Many labels are unwanted program or riskware style (Application.Generic, Riskware/Crack, Generic Reputation unwanted program), consistent with a licence crack rather than a classic trojan, though cracks are a common malware carrier.

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
  • 38sandbox rule tags
  • 8spawned processes
  • 13network contacts
  • 34filesystem & mutex artifacts

What the test run showed

What the file did on a test computer

Confirmed in the test run

  • High concern: Created a file that antivirus engines classify as malicious.

  • 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: Unpacked hidden content while it ran.

  • Moderate concern: Checked whether it was running on a test computer.

  • Moderate concern: Hid files or windows on the test computer.

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

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 creating a service; no new service was recorded.

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

Threat context

How cracked-software installers work

A crack or patch installer is one of the most common ways to spread trojans. Even if the program seems to work, it can install malware in the background.

Bottom line:There is no safe copy of a cracked installer: delete it, and get the software from its real publisher.

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

      AdskNLM.exe

      387afcf32a29605744367e07e5867584b18f17e15b36ecf1cee1948efd7cfb3b

      Uploaded file

  2. Processes

    What ran

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

      AdskNLM.exe

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

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

      slui.exe

      C:\Windows\System32\slui.exe -Embedding

      Test run
    3. +1 more recorded observation

  3. Files

    Created or changed

    2
    1. Evidence 4 of 7: Dropped fileWorked out from other results

      82be4ec8ba546ebf1e3448976d06e163e9c4e258301cfceb9ce8a2d76ecbd6ae

      A file it created, rated malicious.

      Files it created
    2. Evidence 5 of 7: Written fileSeen in the test run

      nlm.mst

      C:\Users\<USER>\AppData\Local\Temp\Adsk-NLM\nlm.mst

      Test run
    3. +1 more recorded observation

  4. Network

    Hosts contacted

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

      23.61.241.220

      Contacted during the test run.

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

      23.54.12.97

      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

43 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 partial. Complete means the check returned a usable result; it does not mean the file is safe.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteRisk signal: 43 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 scannerPartial5 of 20 contacted hosts were cross-checked; coverage is incomplete Details for contacted hosts
Signature rulesYARAify community rules + MalwareTips rulesCompleteRisk signal: 5 community YARA rules (2 malware-specific) · 1 MalwareTips behaviour rule Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

Engines that flagged it 43

  • Avast (major engine)Win64:MalwareX-gen [Misc]
  • AVG (major engine)Win64:MalwareX-gen [Misc]
  • Avira (major engine)TR/W64.Agent
  • BitDefender (major engine)Application.Generic.4148291
  • DrWeb (major engine)Trojan.MulDrop30.15904
  • Emsisoft (major engine)Application.Generic.4148291 (B)
  • ESET-NOD32 (major engine)Win64/HackTool.Crack.DT potentially unsafe application
  • F-Secure (major engine)Trojan.TR/W64.Agent
35 more in the full engine list

File fingerprint

Last analyzed
Sep 11, 2026, 5:28 AM UTC
SHA-256
387afcf32a29605744367e07e5867584b18f17e15b36ecf1cee1948efd7cfb3b
SHA-1
4e5404d45c25d2ac22941be9f04fdb7035b78115
MD5
c1a94b4dd036c7e43d76ce1a1894b72f

About this file

AdskNLM.exe is a Win32 EXE file of 7.8 MB.

Type and size
Win32 EXE · 7.8 MB
Signer
UnsignedNo code signature.
First seen
Mar 28, 2025On VirusTotal.
Submitted by
835 distinct sources
Packer
None detected
Entropy
8.00 of 8

First scanned Updated

Chapter 05

Questions & answers

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

Is AdskNLM.exe a virus?
Yes. This copy of AdskNLM.exe (SHA-256 387afcf3…fb3b) is malicious. Other files with the same name can be different, so check the hash. Don't run it. Delete it, then empty the Recycle Bin. 43 of the 71 antivirus engines that checked it flag it. Antivirus engines classify it as a trojan hidden in a cracked-software installer. If you've already run it, see the steps below.
What is AdskNLM.exe?
AdskNLM.exe is a Windows program, about 7.8 MB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Mar 28, 2025.
How many antivirus engines detected AdskNLM.exe?
43 of the 71 antivirus engines that checked it flag AdskNLM.exe, including Microsoft and ESET. We weigh which engines flagged it and what else the scan found, not just the count. In a test run it also created a file that antivirus engines classify as malicious.
What should I do if I already ran AdskNLM.exe?
Act quickly. 1) Disconnect the device from the internet. 2) Run a full scan with your antivirus and let it remove what it finds. 3) Change your important passwords from another device you trust, starting with email and banking, and turn on two-step verification. 4) If you bank or shop on this device, watch your accounts and tell your bank about payments you don't recognise. 5) If the scan keeps finding it, back up your personal files and reinstall Windows.
How do I remove AdskNLM.exe?
To remove AdskNLM.exe: 1) run a full scan with your antivirus and let it remove what it finds. 2) Delete it, then empty the Recycle Bin. 3) Check Settings > Apps, your browser extensions, startup apps (Task Manager > Startup apps) and scheduled tasks for anything you don't recognise. 4) Restart and scan again. If it keeps coming back, scan from Safe Mode with Networking, or back up your files and reinstall Windows.
What kind of malware is AdskNLM.exe?
Antivirus engines classify AdskNLM.exe as a trojan hidden in a cracked-software installer.
What is the SHA-256 hash of AdskNLM.exe?
The SHA-256 fingerprint of AdskNLM.exe is 387afcf32a29605744367e07e5867584b18f17e15b36ecf1cee1948efd7cfb3b, and its MD5 is c1a94b4dd036c7e43d76ce1a1894b72f. 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 AdskNLM.exe?
This report reflects the scan on Sep 11, 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

Other files people checked with the same name, and recent reports with the same rating. A matching name does not make two files the same: only the SHA-256 fingerprint identifies a file.

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.