Is AdskNLM.exe safe?
A confirmed software-crack tool drew 43 of 75 engine detections, exhibited multiple offensive techniques, and dropped a child already identified as malware.
The file is an unsigned crack tool detected by 43 of 75 engines, including 11 high-trust detections and corroborated hacktool labels. Runtime evidence records process-injection and defense-evasion techniques, while one of its ten inspected dropped files is already known to be malware.
387afcf32a29605744…e1948efd7cfb3bRecommended next actions
Before running
Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already ran it
Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
The file is an unsigned crack tool detected by 43 of 75 engines, including 11 high-trust detections and corroborated hacktool labels. Runtime evidence records process-injection and defense-evasion techniques, while one of its ten inspected dropped files is already known to be malware.
ESET-NOD32 and Ikarus identify the sample as a crack hacktool, and the corroboration threshold for offensive tooling is satisfied. Overall, 43 of 75 engines detected it, including 11 high-trust detections and a strong three-engine crack-family consensus. The completed sandbox run recorded six offensive techniques, including process injection (T1055), data destruction (T1485), privilege escalation (T1548), and defense impairment (T1562.001). One of ten inspected dropped children is already known to be malware, independently confirming harmful payload delivery. The executable is unsigned, and neither prevalence nor the absence of a formal sandbox verdict credibly offsets this combined evidence.
What We Detected
The executable was flagged by 43 of 75 antivirus engines, including 11 high-trust detections. ESET-NOD32 and Ikarus specifically identify a crack hacktool, while Microsoft and TrendMicro associate it with Suschil; three high-trust engines independently converge on the crack family.
Threat Behavior
A completed sandbox run recorded six offensive techniques, including process injection (T1055), PowerShell execution (T1059.001), data destruction (T1485), service manipulation (T1543.003), privilege escalation (T1548), and impairment of defenses (T1562.001). The process activity also included deletion of the Autodesk Access startup entry. Most importantly, the executable dropped ten inspected files, and child 82be4ec8ba546ebf1e3448976d06e163e9c4e258301cfceb9ce8a2d76ecbd6ae is already known to be malware.
What To Do Now
Do not run or retain this executable. Keep endpoint protection enabled, quarantine the file and its extracted contents, and perform a full system scan; if it has already run, review persistence, services, credentials, and Autodesk-related licensing components.
Where this verdict could be wrong4 caveats
- behaviour.hasMaliciousSandboxVerdict=false, although the completed run still recorded six offensive techniques and produced a known-malicious child.
- contactedHosts inspected only 5 hosts while behaviour records 15 IPs and 6 URLs, so no complete host-reputation result is available.
- prevalence.classification='common_old' reflects 835 submitters and 920 submissions, but prevalence does not outweigh the confirmed crack labels and malicious dropped child.
- externalIntel.circl.hit=false, while MalwareBazaar and YARAify coverage was skipped; this is not comprehensive external clearance.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- behaviour.hasMaliciousSandboxVerdict=false
- No high-entropy code or likely packing was identified
- The sample is established rather than newly observed
- 43 of 75 antivirus engines detected the file
- 11 high-trust engine detections
- Confirmed crack hacktool labels
- One known-malicious dropped child
- Process injection technique T1055
- Defense impairment technique T1562.001
Quarantine and remove the executable while keeping endpoint protection enabled. If it was executed, run a full scan and investigate dropped files, modified startup settings, services, and possible credential exposure.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete43 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial5 of 25 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete3 signature or behavior rules matched.
External intel
PartialIndependent reference checks were attempted but are incomplete.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 38MITRE ATT&CK techniques
- 15spawned processes
- 26network contacts
- 34filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Drops additional malware files onto your PC when it runs.
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Used an input-capture technique that can record credentials or keystrokes.
High concern: Created or modified a system service, which can keep code running.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
High concern: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Threat context
How hacktools are abused
This is a hacking or cracking tool — the kind used to bypass software licences, generate fake keys, or attack other systems. Even when the tool 'works', these downloads very often carry hidden malware.
Bottom line:Running one means trusting an anonymous author with full access to your PC — rarely worth the risk.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
AdskNLM.exe
387afcf32a29605744367e07e5867584b18f17e15b36ecf1cee1948efd7cfb3b
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\AdskNLM.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\System32\slui.exe -Embedding
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Dropped fileDerived
82be4ec8ba546ebf1e3448976d06e163e9c4e258301cfceb9ce8a2d76ecbd6ae
Saved child-file verdict: malicious.
04Dropped-file analysis - Written fileObserved
nlm.mst
C:\Users\<USER>\AppData\Local\Temp\Adsk-NLM\nlm.mst
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
23.61.241.220
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
23.54.12.97
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 23.61.241.220
- 23.54.12.97
- 192.168.0.14
- 23.55.140.42
- 192.168.0.35
- 23.101.168.44
- 23.196.193.245
- 23.67.33.153
- 184.27.218.92
- 23.96.180.189
- http://www.microsoft.com/pki/certs/MicRooCerAut_2010-06-23.crt
- http://crl.verisign.com/pca3-g5.crl
- http://ocsp.verisign.com/MFEwTzBNMEswSTAJBgUrDgMCGgUABBS56bKHAoUD+Oyl+0LhPg9JxyQm4gQUf9Nlp8Ld7LvwMAnzQzn6Aq8zMTMCEGxZ76nhAOEO4wa6j+ApJVk=
- http://evcs-ocsp.ws.symantec.com/MFEwTzBNMEswSTAJBgUrDgMCGgUABBQckPwgwK2Thdm9JYVwXQ4ERz3XDQQUo47PGUI9MeGrIYmEbcvZeaKysloCEHX7Uch2jvaSe/QdoaI0odk=
- http://evcs-crl.ws.symantec.com/evcs.crl
- http://ocsp.verisign.com/
- C:\Users\<USER>\AppData\Local\Temp\Adsk-NLM\nlm.mst
- C:\Users\<USER>\AppData\Local\Temp\Adsk-NLM\UnNamed.json
- C:\Users\<USER>\AppData\Local\Temp\Adsk-NLM\delnowmic.ps1
- C:\Users\<USER>\AppData\Local\Temp\Adsk-NLM\nlm11-19-4-1-ipv4-ipv6-win64.msi
- C:\Users\<USER>\AppData\Local\Temp\Adsk-NLM\licenses.lic
- C:\Users\<USER>\AppData\Local\Temp\Adsk-NLM\adskflex.exe
- C:\Users\<USER>\AppData\Local\Temp\Adsk-NLM\delnowmic.ps1
- C:\Users\<USER>\AppData\Local\Temp\Adsk-NLM\licenses.lic
- C:\Users\<USER>\AppData\Local\Temp\Adsk-NLM\nlm.mst
- C:\Users\<USER>\AppData\Local\Temp\Adsk-NLM\nlm11-19-4-1-ipv4-ipv6-win64.msi
- Local\ZonesCacheCounterMutex
- Local\ZonesLockedCacheCounterMutex
- \Sessions\1\BaseNamedObjects\Local\ZoneAttributeCacheCounterMutex
- \Sessions\1\BaseNamedObjects\Local\SessionImmersiveColorMutex
Files this sample writes at runtime
The sandbox saw this file drop 10 children. 1 of them is already known-malicious in our database — this file is a dropper.
- 6f13e52d797a732435c8…6cc95fNever scannednever seen before
- c6a4426b196f19b0a456…4ba6dbNever scannednever seen before
- 82be4ec8ba546ebf1e34…cbd6aeMalicious4/72 enginestrust 16from our cache
- 54c993ec37cdc90a8821…3cdbbfNever scannednever seen before
- bc112c7b85466f7852fe…7d4b60Never scannednever seen before
- 90e413cd675ee085c441…672bdbNever scannednever seen before
- 67ac43957233a6ebff21…a8fa71Never scannednever seen before
- e0371582686d18b48edb…711651Never scannednever seen before
- 4606920618e17ec2588f…67dd5aNever scannednever seen before
- 4b5ef379990a4663a334…ff92f9Never scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 3rule hits recorded
- 43 / 75engines flagged
- 835sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
The file created or unpacked 1 malicious payload.
Verdict inputView chapterProvenanceDerivedSourceDropped-file analysisObserved at - 02
2 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
43 of 75 antivirus engines flagged the file, including AhnLab-V3 and alibabacloud.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 04
Scanned file: AdskNLM.exe — 387afcf32a29605744367e07e5867584b18f17e15b36ecf1cee1948efd7cfb3b
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\AdskNLM.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\System32\slui.exe -Embedding
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Dropped file: 82be4ec8ba546ebf1e3448976d06e163e9c4e258301cfceb9ce8a2d76ecbd6ae — Saved child-file verdict: malicious.
ProvenanceDerivedSourceDropped-file analysisObserved at - 08
File written: nlm.mst — C:\Users\<USER>\AppData\Local\Temp\Adsk-NLM\nlm.mst
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 23.61.241.220 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 23.54.12.97 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: hacktool
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -pSandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceSangfor: Hacktool.Win64.Crack.Vc1rThe sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence23.61.241.220 · 23.54.12.97 · 23.55.140.42
43 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- AdskNLM.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 7.4 MB
- Last analyzed
- Sep 11, 2026, 5:28 AM UTC
387afcf32a29605744367e07e5867584b18f17e15b36ecf1cee1948efd7cfb3bSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file is dangerous. Treat it as harmful and remove it.
- Recovery step 01
Don't run this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already ran it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.
- Recovery step 03
From a different, clean device, change the passwords on your important accounts (email and banking first) and turn on two-factor authentication.
- Recovery step 04
It can drop extra files, so run a full system scan — not just a quick one — to catch anything it left behind.
- Recovery step 05
Get a fresh copy from the developer's official site or an official app store.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is AdskNLM.exe a virus?
What is AdskNLM.exe?
How many antivirus engines detected AdskNLM.exe?
What should I do if I already ran AdskNLM.exe?
How do I remove AdskNLM.exe?
What kind of malware is AdskNLM.exe?
What is the SHA-256 hash of AdskNLM.exe?
How up to date is this analysis of AdskNLM.exe?
Community
Member reviews and reports for this exact file hash.