Is 46a483a3-6f07-44b1-a783-873bd4af1ec1 safe?
Runtime analysis recorded injection, persistence, and defense-evasion techniques, while six researcher rules corroborate concerning traits despite minimal antivirus detection.
Completed runtime analysis recorded process injection, persistence, and defense-evasion techniques, and six researcher rules matched the executable. Although only 2 of 75 engines detected it and its observed hosts lacked adverse reputation, the corroborated behavioral evidence makes execution an unacceptable risk.
2e67d5e7d96aec62a9…19723205abba9eRecommended next actions
Before opening
Do not open it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already opened it
Close it. If it opened links, requested credentials, or triggered unexpected behavior, disconnect from the internet and run a full device scan.
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.
Completed runtime analysis recorded process injection, persistence, and defense-evasion techniques, and six researcher rules matched the executable. Although only 2 of 75 engines detected it and its observed hosts lacked adverse reputation, the corroborated behavioral evidence makes execution an unacceptable risk.
Only APEX and Jiangmin flagged the file among 75 engines, and no tier-1 engine detected it, which ordinarily favors a false-positive explanation. However, a completed sandbox run produced a malware assessment and recorded six offensive techniques, including process injection, service or registry persistence, and impairment of defenses. Six researcher rules also matched, including rules for script injection and debugger checks, providing independent static corroboration. The runtime assessments conflict, and all 20 observed hosts lacked malicious or suspicious cache verdicts. Its long history and very high submission count further reduce certainty, but they do not adequately explain the combined injection, persistence, evasion, and researcher-rule evidence.
What We Detected
Two of 75 antivirus engines flagged the executable: APEX used a generic malicious label, while Jiangmin reported Trojan.Generic.gzwsg. Both are low-trust detections, and all 17 reporting tier-1 engines were clean. More importantly, six researcher rules matched, including CP_Script_Inject_Detector, DebuggerCheck__API, AutoIt, and AutoIT_Compiled.
Threat Behavior
Completed runtime analysis produced conflicting assessments, with one malware result and one clean result. The recorded activity nevertheless includes T1055 process injection, T1543.003 service persistence, T1547.001 registry-run persistence, and T1562.001 defense impairment. Host-reputation coverage included all 20 distinct observed contacts and found no malicious or suspicious hosts; none of 10 inspected children had a malicious verdict, although every child remained unclassified.
What To Do Now
Do not run the executable on a production or personal system. Keep endpoint protection enabled, quarantine the file, and obtain a fresh copy only from a verified original publisher if the software is required.
Where this verdict could be wrong5 caveats
- APEX and Jiangmin are the only 2/75 detections, and all 17 reporting tier-1 engines were clean.
- The sandbox evidence conflicts: sandboxVerdicts contains one malicious result and one clean result.
- contactedHosts found no malicious or suspicious entries among all 20 distinct observed hosts.
- The file is old and highly prevalent, with 270398 submissions since 2019, which is atypical for an obscure active trojan.
- The sole similarHashes result is an imphash-only match with signerCoMatch=false, so a shared build framework may explain it.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 2/75 engines detected the file, both low-trust
- All 17 reporting tier-1 engines were clean
- All 20 distinct observed hosts received full reputation coverage with no adverse verdicts
- No malicious child was found among 10 inspected dropped files
- The file has 270398 submissions dating back to 2019
- Completed sandbox analysis produced a malicious assessment
- Runtime evidence maps to T1055 process injection
- Persistence techniques T1543.003 and T1547.001 were recorded
- Defense impairment technique T1562.001 was recorded
- Six YARAify rules matched, including CP_Script_Inject_Detector
- The executable is unsigned
Quarantine the file and do not execute it outside an isolated analysis environment. Keep security protection enabled and replace it with a copy obtained directly from a verified publisher.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete2 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial20 of 40 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete6 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
- 43MITRE ATT&CK techniques
- 15spawned processes
- 40network 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: 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 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
46a483a3-6f07-44b1-a783-873bd4af1ec1
2e67d5e7d96aec62a9dda4c0259167a44908af863c2b3af2a019723205abba9e
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\executable.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\2e67d5e7d96aec62a9dda4c0259167a44908af863c2b3af2a019723205abba9e.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
lzrzvwu
C:\Users\<USER>\AppData\Local\Temp\lzrzvwu
04Isolated runtime analysis - Written fileObserved
playback.ico
C:\Users\<USER>\Desktop\ACLib\playback.ico
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
query.prod.cms.rt.microsoft.com
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostDerived
www.microsoft.com
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.
- query.prod.cms.rt.microsoft.com
- www.microsoft.com
- res.public.onecdn.static.microsoft
- crt.sectigo.com
- 129.214.248.87.in-addr.arpa
- 212.143.182.52.in-addr.arpa
- fp2E7A.wpc.2BE4.phicdn.net
- 173.117.168.52.in-addr.arpa
- 106.89.54.20.in-addr.arpa
- firefox.settings.services.mozilla.com
- 20.80.129.13
- a83f:8110:0:0:40b3:2be5:8d02:0
- 13.107.39.203
- 192.168.0.159
- a83f:8110:0:0:9e01:0:0:0
- a83f:8110:0:0:1b00:100:2800:0
- a83f:8110:584a:b5b1:17cb:1ec8:0:0
- 23.216.147.76
- 23.216.147.64
- a83f:8110:7900:eee4:f8ff:ffff:10f3:7000
- HKLM\Software\Microsoft\WBEM\CIMOM\ConfigValueEssNeedsLoading
- HKLM\Software\Microsoft\WBEM\CIMOM\List of event-active namespaces
- \\Registry\Machine\Software\Microsoft\Windows NT\CurrentVersion\Time Zones\Greenland Standard Time\TZI
- \\Registry\Machine\Software\Microsoft\Windows NT\CurrentVersion\Time Zones\Iran Standard Time\TZI
- HKLM\SYSTEM\ControlSet001\Control\BackupRestore\FilesNotToBackup\BITS_LOG
- HKLM\SYSTEM\ControlSet001\Control\BackupRestore\FilesNotToBackup\BITS_BAK
- C:\Users\<USER>\AppData\Local\Temp\lzrzvwu
- C:\Users\<USER>\Desktop\ACLib\playback.ico
- C:\Users\<USER>\Desktop\ACLib\record.ico
- C:\Users\<USER>\Desktop\ACLib\stop.ico
- C:\Documents and Settings\Administrator\Local Settings\Temp\sagslmr
- C:\Users\<USER>\AppData\Local\Temp\lzrzvwu
- %USERPROFILE%\AppData\Local\Temp\voondgv
- %USERPROFILE%\AppData\Local\Temp\pelsajm
- %USERPROFILE%\AppData\Local\Temp\pwvcobs
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E6.tmp.WERInternalMetadata.xml
- CTF.LBES.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Compart.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Asm.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Layouts.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.TMD.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 5375290e66a20bff81fb…3fe80dNever scannednever seen before
- 9e869f60ea0a0de06c7d…649483Never scannednever seen before
- d41b2aa7a6a3cd2c42ae…74fdf8Never scannednever seen before
- 59d5e9106e907fa61a56…7287a6Never scannednever seen before
- e434d77840c716acd21c…c09b18Never scannednever seen before
- 2131ca637e847ed5f653…b5d153Never scannednever seen before
- 6da4accec2beaf142ae8…94a737Never scannednever seen before
- dd40056d24275879ca12…8b245bNever scannednever seen before
- e3b0c44298fc1c149afb…52b855Never scannednever seen before
- bb5a1d709ddba97bb438…d77afaNever 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.
- 6rule hits recorded
- 2 / 75engines flagged
- 3,725sources 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
6 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
2 of 75 antivirus engines flagged the file, including APEX and Jiangmin.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 04
Scanned file: 46a483a3-6f07-44b1-a783-873bd4af1ec1 — 2e67d5e7d96aec62a9dda4c0259167a44908af863c2b3af2a019723205abba9e
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\executable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\2e67d5e7d96aec62a9dda4c0259167a44908af863c2b3af2a019723205abba9e.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: lzrzvwu — C:\Users\<USER>\AppData\Local\Temp\lzrzvwu
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: playback.ico — C:\Users\<USER>\Desktop\ACLib\playback.ico
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: query.prod.cms.rt.microsoft.com — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: www.microsoft.com — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved at
Detection sources at a glance
Category: generic-trojan
One or more independent reference databases matched 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.
- AutoIt
- AutoIT_Compiled
- CP_Script_Inject_Detector
- DebuggerCheck__API
- golang_bin_JCorn_CSC846
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.
Evidence"C:\Users\<USER>\Desktop\executable.exe"
2 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
- 46a483a3-6f07-44b1-a783-873bd4af1ec1
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 844.1 KB
- Last analyzed
- Oct 8, 2026, 8:51 AM UTC
2e67d5e7d96aec62a9dda4c0259167a44908af863c2b3af2a019723205abba9eSafety & 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 open this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already opened 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 original trusted source and verify its exact hash when possible.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is 46a483a3-6f07-44b1-a783-873bd4af1ec1 a virus?
What is 46a483a3-6f07-44b1-a783-873bd4af1ec1?
How many antivirus engines detected 46a483a3-6f07-44b1-a783-873bd4af1ec1?
What should I do if I already opened 46a483a3-6f07-44b1-a783-873bd4af1ec1?
How do I remove 46a483a3-6f07-44b1-a783-873bd4af1ec1?
What kind of malware is 46a483a3-6f07-44b1-a783-873bd4af1ec1?
What is the SHA-256 hash of 46a483a3-6f07-44b1-a783-873bd4af1ec1?
How up to date is this analysis of 46a483a3-6f07-44b1-a783-873bd4af1ec1?
Community
Member reviews and reports for this exact file hash.