Is impulsum-12-0.9.1.exe safe?
Unsigned executable flagged by seven tier-1 engines as Draftor variant with process-injection and LSASS-access behaviour.
31 of 75 engines detect this file, including seven tier-1 engines that label it a Draftor-family trojan. Sandbox evidence shows process injection (T1055) and LSASS access (T1548), and the file is unsigned with no prior reputation.
81ed1f74644ffe0312…7c2b986c04e57bRecommended 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.
31 of 75 engines detect this file, including seven tier-1 engines that label it a Draftor-family trojan. Sandbox evidence shows process injection (T1055) and LSASS access (T1548), and the file is unsigned with no prior reputation.
The combination of tier-1 consensus on the Draftor family, offensive MITRE techniques observed in sandbox, and the complete absence of code signing or established signer history outweighs the medium prevalence and lack of external-intel corroboration. The file is newly submitted and shows no test-file or hacktool labels that would alter the classification.
What We Detected
Seven tier-11 engines (Avast, AVG, Avira, BitDefender, Emsisoft, F-Secure, GData, Microsoft, Sophos, Symantec, TrendMicro-HouseCall) flag the sample as malicious, with multiple detections converging on the Draftor family. Sandbox execution recorded process-injection activity (T1055) and credential-dumping behaviour targeting LSASS (T1548).
Threat Behavior
The executable is unsigned and newly observed. It writes files under the user profile and creates multiple mutexes associated with Windows Explorer icon caches. No external C2 domains were recorded in the available sandbox trace, but the offensive MITRE techniques alone are inconsistent with legitimate software.
What To Do Now
Do not execute the file. Keep endpoint protection enabled and submit the sample to your security vendor for further analysis if additional context is required.
- 7 tier-1 engines flag the sample
- Process injection (T1055) and LSASS access (T1548) observed
- Unsigned executable with zero signer history
- Newly submitted file (0 days old)
Block the file and investigate any systems where it has already been executed.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete31 of 75 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
- 19MITRE 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: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
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
impulsum-12-0.9.1.exe
81ed1f74644ffe031213995e7f8a9847a5ee1fba6d2857a9587c2b986c04e57b
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\program.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
Explorer
C:\Users\user\AppData\Local\Microsoft\Windows\Explorer
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\Microsoft\Windows\Explorer
- Global\OneSettingQueryMutex+compat+encapsulation
- \Sessions\1\BaseNamedObjects\Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:iconcache_idx.db!rwWriterMutex
- \Sessions\1\BaseNamedObjects\Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:iconcache_16.db!dfMaintainer
- \Sessions\1\BaseNamedObjects\Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:iconcache_32.db!dfMaintainer
- \Sessions\1\BaseNamedObjects\Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:iconcache_48.db!dfMaintainer
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
- 31 / 75engines flagged
- 27sources 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
31 of 75 antivirus engines flagged the file, including ALYac and APEX.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 31 times from 27 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: impulsum-12-0.9.1.exe — 81ed1f74644ffe031213995e7f8a9847a5ee1fba6d2857a9587c2b986c04e57b
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\program.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: Explorer — C:\Users\user\AppData\Local\Microsoft\Windows\Explorer
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
31 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- impulsum-12-0.9.1.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 8.9 MB
- Last analyzed
- Sep 2, 2026, 7:25 PM UTC
81ed1f74644ffe031213995e7f8a9847a5ee1fba6d2857a9587c2b986c04e57bSafety & 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 impulsum-12-0.9.1.exe malware?
What is impulsum-12-0.9.1.exe?
How many antivirus engines detected impulsum-12-0.9.1.exe?
I already downloaded and ran impulsum-12-0.9.1.exe — what should I do?
How do I remove impulsum-12-0.9.1.exe?
What kind of malware is impulsum-12-0.9.1.exe?
What is the SHA-256 hash of impulsum-12-0.9.1.exe?
How up to date is this analysis of impulsum-12-0.9.1.exe?
Community
Member reviews and reports for this exact file hash.