Is AdskNLM.exe safe?
Four high-trust engines detected this unsigned executable, while runtime evidence shows process-injection, privilege-elevation, defense-evasion, and LSASS-targeting activity consistent with hostile crack tooling.
The file drew detections from 14 of 74 engines, including four high-trust products, and it lacks a verified signature. Runtime evidence includes T1055 process injection, T1548 privilege elevation, T1562.001 defense impairment, and activity involving LSASS; avoid running it and remove it if already downloaded.
2624ee98c331339a95…9ff795384b1834Recommended 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 drew detections from 14 of 74 engines, including four high-trust products, and it lacks a verified signature. Runtime evidence includes T1055 process injection, T1548 privilege elevation, T1562.001 defense impairment, and activity involving LSASS; avoid running it and remove it if already downloaded.
Four high-trust engines are among the 14 of 74 products detecting the executable, which is too strong to dismiss as low-quality heuristic noise. The file is unsigned and has no established publisher history. A completed sandbox run recorded three offensive techniques—T1055, T1548, and T1562.001—and saved evidence also associates the process activity with LSASS. Two earlier files sharing its imphash and filename received malicious crack-tool assessments, although imphash-only matches are supporting evidence rather than proof. No strong engine consensus establishes a precise family, and the hacktool label is not sufficiently corroborated for a confirmed hacktool attribution.
What We Detected
Fourteen of 74 antivirus engines flagged the executable, including Microsoft, Ikarus, Sophos, and Symantec among the high-trust products. Labels range from Wacatac and Agent to ABApplication, crack tooling, and generic machine-learning detections, so the engines do not establish one precise family. The Win32 executable is unsigned and has no publisher history that would counterbalance these findings.
Threat Behavior
One completed sandbox observation mapped activity to T1055 process injection, T1548 privilege elevation, and T1562.001 impairment of defenses. Saved process evidence also indicates activity involving LSASS, a sensitive credential-store process. The sample wrote multiple components, including a PowerShell script, an installer, and secur32.dll; the ten dropped hashes have not received confirmed child verdicts. No complete contacted-host reputation result is available, although the recorded run contains no listed network contacts.
What To Do Now
Do not execute the file, especially on a production or personal system containing credentials. Keep endpoint protection enabled, quarantine or delete the sample, and run a full scan if it was launched. If execution occurred, review the host for credential access, injected processes, altered security settings, and unauthorized software-license modifications.
Where this verdict could be wrong4 caveats
- 12 tier-1 engines reported no detection, and tier1FamilyConsensus.strong=false, so the high-trust engines do not agree on a specific family.
- behaviour.hasMaliciousSandboxVerdict=false, and all 10 inspected dropped children remain unknown rather than confirmed malicious.
- externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false; these absences may reflect coverage gaps rather than exoneration.
- contactedHosts=null, so no complete contacted-host reputation result is available.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No strong tier-1 family consensus
- behaviour.hasMaliciousSandboxVerdict=false
- No inspected child was confirmed malicious
- No CIRCL, MalwareBazaar, or YARAify match
- PE code sections were not identified as packed or high-entropy
- 14/74 antivirus detections
- Four high-trust engine detections
- Unsigned Win32 executable
- T1055 process-injection evidence
- T1548 privilege-elevation evidence
- T1562.001 defense-evasion evidence
Do not run this executable; quarantine or delete it while keeping endpoint protection enabled. If it has already executed, perform a full security scan and treat credentials used on that system as potentially exposed.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete14 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
Complete2 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 21MITRE ATT&CK techniques
- 11spawned processes
- 0network contacts
- 12filesystem & mutex artifacts
What this file does
Observed actions and their security significance
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: 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.
Moderate concern: Runs hidden system commands (script or shell).
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 trojans work
A trojan disguises itself as something useful or harmless to trick you into running it. Once open, it does its real job in the background — anything from stealing data to opening a back door or downloading more malware.
Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.
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
2624ee98c331339a95ef7a45e6e9ed82b83c8b82157c0481c99ff795384b1834
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\AdskNLM.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Caches
C:\Users\user\AppData\Local\Microsoft\Windows\Caches
04Isolated runtime analysis - Written fileObserved
Adsk-NLM
C:\Users\user\AppData\Local\Temp\Adsk-NLM
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- C:\Users\user\AppData\Local\Microsoft\Windows\Caches
- C:\Users\user\AppData\Local\Temp\Adsk-NLM
- C:\Users\user\AppData\Local\Temp\Adsk-NLM\UnNamed.json
- C:\Users\user\AppData\Local\Temp\Adsk-NLM\adskflex.exe
- C:\Users\user\AppData\Local\Temp\Adsk-NLM\delnowmic.ps1
- Global\OneSettingQueryMutex+compat+encapsulation
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 1757a57efa0a09a6788a…bfea57Never scannednever seen before
- 6e3df38608c576ef7df1…1f729fNever scannednever seen before
- d90c4738a07c16425772…e2efe7Never scannednever seen before
- 74b3152a28d4f1a4fff4…89ff70Never scannednever seen before
- 3a053653cd79ba09f459…01c28dNever scannednever seen before
- 08bf71723f17bc3bb3d0…79af7eNever scannednever seen before
- 32ee791aa61bfe60a28a…62fcc1Never scannednever seen before
- 6f13e52d797a732435c8…6cc95fNever scannednever seen before
- a9cedb4084f243ff831c…a9fbe7Never scannednever seen before
- 99809f4edba150684036…6bd857Never 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.
- 2rule hits recorded
- 14 / 74engines flagged
- 13sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
14 of 74 antivirus engines flagged the file, including CrowdStrike and Cylance.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 13 times from 13 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: AdskNLM.exe — 2624ee98c331339a95ef7a45e6e9ed82b83c8b82157c0481c99ff795384b1834
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\AdskNLM.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Caches — C:\Users\user\AppData\Local\Microsoft\Windows\Caches
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Adsk-NLM — C:\Users\user\AppData\Local\Temp\Adsk-NLM
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: generic-trojan
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
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.
EvidenceC:\Windows\system32\lsass.exe
14 of 74 engines flagged this file
View all 74 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- AdskNLM.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 7.9 MB
- Last analyzed
- Sep 20, 2026, 8:50 AM UTC
2624ee98c331339a95ef7a45e6e9ed82b83c8b82157c0481c99ff795384b1834Safety & 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
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 malware?
What is AdskNLM.exe?
How many antivirus engines detected AdskNLM.exe?
I already downloaded and ran AdskNLM.exe — what should I do?
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.