Is micro-with-editor.exe safe?
No antivirus engine detected the signed, widely distributed file, but one sandbox reported injection-like and LSASS-targeting activity that warrants caution.
All 75 antivirus engines were silent, including 17 high-trust engines, and the file has circulated widely for nearly two years. However, one completed sandbox produced a malicious assessment and mapped activity to process injection and LSASS access, so the executable should not be trusted without further verification.
38b2c529df14546b32…f4e1854cff8a6cRecommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
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.
All 75 antivirus engines were silent, including 17 high-trust engines, and the file has circulated widely for nearly two years. However, one completed sandbox produced a malicious assessment and mapped activity to process injection and LSASS access, so the executable should not be trusted without further verification.
Static evidence is favorable because 0 of 75 antivirus engines detected the file, including all 17 tier-1 engines. It is also verified-signed and has been submitted 7,193 times by 3,573 sources, making an undetected widespread trojan less likely. Runtime evidence conflicts with that picture: one sandbox assessment was malicious, T1055 process injection was mapped, and another heuristic reported access involving LSASS. The sandbox results themselves disagree, and none of the ten dropped files received a confirmed malicious classification. Host-reputation coverage was incomplete because only three domains were inspected while many IP contacts were recorded, so the network evidence cannot resolve the conflict. Overall, the runtime findings justify isolation and independent validation despite the strong static evidence suggesting a possible behavioral false positive.
What We Detected
The antivirus network reported 0 detections out of 75 engines, with all 17 tier-1 engines silent. The executable carries a verified signature from AMSTION LIMITED and is not identified as packed or high-entropy code. It is also well established, with 7,193 submissions from 3,573 sources over 655 days.
Threat Behavior
One completed sandbox produced conflicting assessments: one malicious and one clean. The recorded activity includes MITRE T1055 process injection and several other offensive techniques, while a heuristic cites interaction involving LSASS, which can indicate credential-access behavior. No malicious dropped child was identified, but all ten children remain unclassified. Three contacted domains were checked without a cached threat finding, although the numerous observed IP contacts were not fully covered, so no complete host-reputation conclusion is available.
What To Do Now
Keep endpoint protection enabled and quarantine the executable until its origin and publisher can be independently verified. If it came directly from the expected vendor, obtain a fresh copy through that vendor's official release channel and compare its SHA-256 hash and signature before execution.
Where this verdict could be wrong5 caveats
- The antivirus result is uniformly favorable: 0/75 engines detected malware, including no detections from 17 tier-1 engines.
- The file is verified-signed by 'AMSTION LIMITED' and peAnalysis.likelyPacked=false, reducing two common static risk indicators.
- The sandbox evidence is internally mixed: behaviour.sandboxVerdicts contains both a malicious and a clean result.
- contactedHosts lists no cached malicious or suspicious host among three inspected domains, but numerous observed IP contacts were not covered.
- droppedChildren.hasMaliciousChild=false, although all 10 child verdicts are unknown rather than confirmed clean.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/75 antivirus engines detected the file
- All 17 tier-1 engines reported no detection
- Verified signature from AMSTION LIMITED
- 7,193 submissions from 3,573 sources
- peAnalysis.likelyPacked=false and highEntropyCode=false
- behaviour.hasMaliciousSandboxVerdict=true
- MITRE T1055 process-injection mapping
- Heuristic evidence references lsass.exe access
- Seven offensive MITRE techniques were recorded
- The signer has no established history in signing.signerStats
- Contacted-host reputation coverage is incomplete
Keep the file quarantined and endpoint protection enabled while verifying its source and signature against an official vendor download. Do not run it on a production system until the conflicting sandbox behavior is resolved.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial3 of 23 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete2 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
- 29MITRE ATT&CK techniques
- 15spawned processes
- 23network contacts
- 40filesystem & 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: 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: Manipulated how the operating system loads code, which can redirect execution.
High concern: Loaded code directly into memory instead of from a normal file.
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.
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
micro-with-editor.exe
38b2c529df14546b32814aa6d4deddb239d5312a6157be3396f4e1854cff8a6c
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\program.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-QLH27.tmp\program.tmp" /SL5="$1F001A,2005345,57856,C:\Users\<USER>\Desktop\program.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
program.tmp
C:\Users\<USER>\AppData\Local\Temp\is-QLH27.tmp\program.tmp
04Isolated runtime analysis - Written fileObserved
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-HTVG8.tmp\_isetup\_setup64.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostDerived
www.microsoft.com
Saved reputation verdict: safe.
06Contacted-host cross-check - Contacted hostDerived
res.public.onecdn.static.microsoft
Saved reputation verdict: safe.
07Contacted-host cross-check - +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; 1 returned "malicious".
Adversary techniques mapped to the MITRE ATT&CK framework.
- www.microsoft.com
- res.public.onecdn.static.microsoft
- ocsps.ssl.com
- 23.216.81.152
- 20.99.186.246
- 104.98.118.160
- 20.99.185.48
- a83f:8110:7800:0:1400:0:4e00:6500
- 192.168.0.40
- 52.185.73.156
- 23.55.140.42
- 23.215.176.129
- 192.168.0.17
- HKEY_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\Software\Microsoft\RestartManager\Session0000\Owner
- HKEY_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\Software\Microsoft\RestartManager\Session0000\Sequence
- HKEY_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\Software\Microsoft\RestartManager\Session0000\SessionHash
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\RestartManager\Session0000\RegFiles0000
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\RestartManager\Session0000\RegFilesHash
- HKEY_CURRENT_USER\Software\Classes\.rms\(Default)
- C:\Users\<USER>\AppData\Local\Temp\is-QLH27.tmp\program.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-HTVG8.tmp\_isetup\_setup64.tmp
- C:\Users\<USER>\AppData\Roaming\AutomaticSolution Software\ReMouse Micro\ReMouse.exe
- C:\Users\<USER>\AppData\Roaming\AutomaticSolution Software\ReMouse Micro\conf\ext\editor_icons.dll
- C:\Users\<USER>\AppData\Roaming\AutomaticSolution Software\ReMouse Micro\ReMouseMode.exe
- C:\Users\<USER>\AppData\Roaming\AutomaticSolution Software\ReMouse Micro\is-4CV70.tmp
- C:\Users\<USER>\AppData\Roaming\AutomaticSolution Software\ReMouse Micro\is-020NV.tmp
- C:\Users\<USER>\AppData\Roaming\AutomaticSolution Software\ReMouse Micro\is-T4V90.tmp
- C:\Users\<USER>\AppData\Roaming\AutomaticSolution Software\ReMouse Micro\is-3OIBE.tmp
- C:\Users\<USER>\AppData\Roaming\AutomaticSolution Software\ReMouse Micro\conf\is-A7TPR.tmp
- cversions.3.m
- Local\MSCTF.Asm.MutexDefault1
- Local\RstrMgr3887CAB8-533F-4C85-B0DC-3E5639F8D511
- Local\RstrMgr-3887CAB8-533F-4C85-B0DC-3E5639F8D511-Session0000
- DefaultTabtip-MainUI
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- cc783a04ccbca4edd065…0d98f3Never scannednever seen before
- bd5503f6f8729868e5e9…46ec6cNever scannednever seen before
- 793dcb17e6cad2895ada…886a56Never scannednever seen before
- 388a796580234efc95f3…136f95Never scannednever seen before
- 642e73db388ec7901017…302842Never scannednever seen before
- 488f88724e7387da2222…87e406Never scannednever seen before
- 13b0c0576a0158fbee6c…9190e9Never scannednever seen before
- 57caac3d73ea5d754c74…0ce911Never scannednever seen before
- 5c6a63cd97a6be43bcd0…db5888Never scannednever seen before
- 71fde503c26e9bfbde60…0de3f7Never 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
- 0 / 75engines flagged
- 3,573sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 isolated runtime environment classified the observed behavior as malicious.
Verdict inputView chapterProvenanceObservedSourceIsolated runtime analysisObserved at - 02
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 04
Scanned file: micro-with-editor.exe — 38b2c529df14546b32814aa6d4deddb239d5312a6157be3396f4e1854cff8a6c
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\program.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-QLH27.tmp\program.tmp" /SL5="$1F001A,2005345,57856,C:\Users\<USER>\Desktop\program.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: program.tmp — C:\Users\<USER>\AppData\Local\Temp\is-QLH27.tmp\program.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _setup64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-HTVG8.tmp\_isetup\_setup64.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: www.microsoft.com — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved at - 10
Contacted host: res.public.onecdn.static.microsoft — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
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\Explorer.EXESandbox 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
0 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
- micro-with-editor.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: AMSTION LIMITED
- Size
- 2.2 MB
- Last analyzed
- Oct 3, 2026, 11:18 AM UTC
38b2c529df14546b32814aa6d4deddb239d5312a6157be3396f4e1854cff8a6cSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't run it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is micro-with-editor.exe safe, or is it malware?
What is micro-with-editor.exe?
How many antivirus engines detected micro-with-editor.exe?
What should I do if I already ran micro-with-editor.exe?
How do I remove micro-with-editor.exe?
Is micro-with-editor.exe digitally signed?
What is the SHA-256 hash of micro-with-editor.exe?
How up to date is this analysis of micro-with-editor.exe?
Community
Member reviews and reports for this exact file hash.