Our call: Is AdskNLM.exe safe?Malicious
Unsigned 7.8 MB executable flagged by 9 tier-1 engines as a confirmed crack/hacktool with 5 offensive MITRE techniques.
- 40 of 75 antivirus engines flagged the file, including ALYac and Arcabit.Observed · Antivirus analysis
- The hash has a long, established submission history across 783 sources.Derived · Submission history
- The hash has been submitted 965 times from 783 sources.Derived · Saved report facts
e2dd28c2f6c6170255…24eaf572b9Recommended 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.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete40 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
Complete1 signature or behavior rule matched.
External intel
PartialIndependent reference checks were attempted but are incomplete.
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
e2dd28c2f6c61702551eb6f8aec59a127bb50c186cea0e068f03f024eaf572b9
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\AdskNLM.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Windows\System32\reg.exe" delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run" /v "Autodesk Access" /f
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
nlm.mst
C:\Users\<USER>\AppData\Local\Temp\Adsk-NLM\nlm.mst
04Isolated runtime analysis - Written fileObserved
UnNamed.json
C:\Users\<USER>\AppData\Local\Temp\Adsk-NLM\UnNamed.json
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
152.199.19.74
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
192.229.221.95
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.
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
40 of 75 antivirus engines flagged the file, including ALYac and Arcabit.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 783 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 03
The hash has been submitted 965 times from 783 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: AdskNLM.exe — e2dd28c2f6c61702551eb6f8aec59a127bb50c186cea0e068f03f024eaf572b9
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\AdskNLM.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Windows\System32\reg.exe" delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run" /v "Autodesk Access" /f
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: nlm.mst — C:\Users\<USER>\AppData\Local\Temp\Adsk-NLM\nlm.mst
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: UnNamed.json — C:\Users\<USER>\AppData\Local\Temp\Adsk-NLM\UnNamed.json
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 152.199.19.74 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 192.229.221.95 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
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.
40 of 75 engines flag the file, including 9 tier-1 detections that label it a crack tool. The sample is unsigned, exhibits 5 offensive MITRE techniques, and hacktoolConfirmed is true. Prevalence is common_old, indicating a widely distributed cracking utility.
The combination of 9 tier-1 malicious detections, explicit hacktool labels from ESET-NOD32 and Ikarus, and 5 offensive MITRE techniques meets the hacktoolConfirmed rule. The file is unsigned with no signer history, removing any benign-publisher benefit. While sandbox and dropped-child checks returned no additional malicious signals, the engine consensus and confirmed hacktool category outweigh those neutral findings.
What We Detected
40 of 75 engines reported the sample malicious. Nine tier-1 engines contributed, with ESET-NOD32 and Ikarus explicitly labeling it a crack/hacktool. The file is a 7.8 MB unsigned Win32 EXE first seen 910 days ago and remains common_old (783 sources).
Threat Behavior
Runtime traces show five offensive MITRE techniques: T1059.001 (PowerShell), T1543.003 (Windows Service), T1547.001 (Registry/Startup), T1548 (Elevation), and T1562.001 (Disable Security Tools). Direct-IP traffic was observed, but contacted-host reputation cross-check found no known-malicious endpoints.
What To Do Now
Do not execute or distribute this file. Keep endpoint protection enabled; the sample is a confirmed cracking utility that attempts to tamper with Autodesk licensing components.
Where this verdict could be wrong3 caveats
- contactedHosts.maliciousHosts.length=0 and droppedChildren.hasMaliciousChild=false — no observed malicious network or child-file corroboration.
- behaviour.hasMaliciousSandboxVerdict=false — sandbox did not return an explicit malicious verdict despite offensive techniques.
- communityComments contain mixed researcher annotations; one comment states the file is used to crack Autodesk products without confirming active harm.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- contactedHosts.maliciousHosts.length=0
- droppedChildren.hasMaliciousChild=false
- behaviour.hasMaliciousSandboxVerdict=false
- Unsigned executable
- 9 tier-1 malicious detections
- hacktoolConfirmed=true
- 5 offensive MITRE techniques
- Direct-IP traffic without domain resolution
Block or delete the file; do not run cracking utilities as they are inherently malicious regardless of claimed purpose.
Behavior
Plain-English impact first, then the observed runtime evidence.
What this file does
Observed actions and their security significance
High concern: Used an input-capture technique that can record credentials or keystrokes.
High concern: Used removable-media replication behaviour that can spread files between devices.
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.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
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.
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.
- 152.199.19.74
- 192.229.221.95
- 104.123.41.162
- 93.184.221.240
- 20.99.186.246
- 192.229.211.108
- 184.25.191.235
- 20.99.184.37
- 20.99.185.48
- 20.99.133.109
- http://ocsp.verisign.com/MFEwTzBNMEswSTAJBgUrDgMCGgUABBS56bKHAoUD+Oyl+0LhPg9JxyQm4gQUf9Nlp8Ld7LvwMAnzQzn6Aq8zMTMCEGxZ76nhAOEO4wa6j+ApJVk=
- http://evcs-ocsp.ws.symantec.com/MFEwTzBNMEswSTAJBgUrDgMCGgUABBQckPwgwK2Thdm9JYVwXQ4ERz3XDQQUo47PGUI9MeGrIYmEbcvZeaKysloCEHX7Uch2jvaSe/QdoaI0odk=
- http://crl.verisign.com/pca3-g5.crl
- http://evcs-crl.ws.symantec.com/evcs.crl
- http://www.microsoft.com/pki/certs/MicRooCerAut_2010-06-23.crt
- http://www.microsoft.com/pki/certs/MicRooCerAut2011_2011_03_22.crt
- 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
- Local\MSCTF.Asm.MutexDefault1
- \Sessions\1\BaseNamedObjects\Global\SyncRootManager
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 4739abff4da13a27f242…d1d365Never scannednever seen before
- 6f13e52d797a732435c8…6cc95fNever scannednever seen before
- 82be4ec8ba546ebf1e34…cbd6aeNever scannednever seen before
- 54c993ec37cdc90a8821…3cdbbfNever scannednever seen before
- 90e413cd675ee085c441…672bdbNever scannednever seen before
- a3f468aebcde57c7ff5a…0ef643Never scannednever seen before
- 67ac43957233a6ebff21…a8fa71Never scannednever seen before
- e0371582686d18b48edb…711651Never scannednever seen before
- 4b5ef379990a4663a334…ff92f9Never scannednever seen before
- c6456e12e5e53287a547…3d144dNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
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
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
The 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.
Evidence152.199.19.74 · 192.229.221.95 · 104.123.41.162
40 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
- Jul 30, 2026, 8:12 AM UTC
e2dd28c2f6c61702551eb6f8aec59a127bb50c186cea0e068f03f024eaf572b9Safety & 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.
Don't run this file. Delete this file from the device, then empty the Recycle Bin or Trash.
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.
From a different, clean device, change the passwords on your important accounts (email and banking first) and turn on two-factor authentication.
Get a fresh copy from the developer's official site or an official app store.