Is WeMacro.exe safe?
Unsigned executable with process-injection and direct-IP sandbox signals but zero AV detections.
No antivirus engine flagged the file, yet sandbox evidence shows process injection (T1055) and direct-IP traffic. Similar imphash samples have mixed verdicts, and the file remains rare after 631 days.
27b856522c1b8972e1…4e645ffaeec5d7Recommended 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.
No antivirus engine flagged the file, yet sandbox evidence shows process injection (T1055) and direct-IP traffic. Similar imphash samples have mixed verdicts, and the file remains rare after 631 days.
Zero detections from 76 engines, including 18 tier-1 scanners, is a strong clean signal. However, the sandbox recorded MITRE techniques T1055 and T1562.001, and two heuristics explicitly map to process injection and direct-IP C2. The imphash matches prior samples with conflicting verdicts, and the file is unsigned with no established signer history. Because the behavioural evidence conflicts with the complete absence of engine detections, the file sits in mixed-signal territory.
What We Detected
76 engines scanned the sample; none returned a malicious or suspicious result. The executable is unsigned. Sandbox execution recorded process-injection (T1055) and defense-evasion (T1562.001) activity plus direct-IP connections to three external addresses.
Threat Behavior
The observed techniques are consistent with both legitimate administrative tools and certain malware families. No dropped children, persistence mechanisms, or known malicious hosts were identified. Host-reputation data for the contacted IPs is unavailable.
What To Do Now
Keep Windows Defender and other endpoint protection enabled. If the file’s origin is untrusted, avoid execution until further reputation data or a code-signature becomes available.
Where this verdict could be wrong1 caveat
- Zero engine detections across 76 scanners provides strong counter-signal to the behavioural heuristics.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero detections across 76 engines
- No tier-1 malicious flags
- No dropped malicious children
- Unsigned PE
- Sandbox shows T1055 process injection
- Direct-IP traffic without domain resolution
- Rare prevalence after 631 days
Treat as untrusted; do not run without additional verification or a trusted digital signature.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial4 runtime contacts were observed without a completed reputation cross-check.
YARA
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
- 18MITRE ATT&CK techniques
- 3spawned processes
- 4network contacts
- 3filesystem & 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: 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: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
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
WeMacro.exe
27b856522c1b8972e1b2f65370494d86207fd0fd98b36cf02b4e645ffaeec5d7
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\executable.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\27b856522c1b8972e1b2f65370494d86207fd0fd98b36cf02b4e645ffaeec5d7.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Roaming
C:\Users\user\AppData\Roaming
04Isolated runtime analysis
Network
Hosts contacted
- Contacted hostObserved
173.194.195.94
Contact observed during runtime.
05Isolated runtime analysis - Contacted hostObserved
192.168.0.32
Contact observed during runtime.
06Isolated runtime analysis - +1 more recorded observation in Analyst mode
6 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.
- 173.194.195.94
- 192.168.0.32
- 20.99.133.109
- 23.216.81.152
- C:\Users\user\AppData\Roaming
- C:\Windows\System32\wbem\Performance\WmiApRpl.h
- C:\Windows\System32\wbem\Performance\WmiApRpl.ini
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 / 76engines flagged
- 1sources 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
0 of 76 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: WeMacro.exe — 27b856522c1b8972e1b2f65370494d86207fd0fd98b36cf02b4e645ffaeec5d7
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\executable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\27b856522c1b8972e1b2f65370494d86207fd0fd98b36cf02b4e645ffaeec5d7.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Roaming — C:\Users\user\AppData\Roaming
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 173.194.195.94 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 192.168.0.32 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
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.
Evidence"C:\Users\<USER>\Desktop\executable.exe"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.
Evidence173.194.195.94 · 20.99.133.109 · 23.216.81.152
0 of 76 engines flagged this file
View all 76 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
Rarely uploaded, but has been around for a while. Often niche legitimate software or old internal tooling; not a strong malware signal on its own.
Fingerprint and provenance
- File name
- WeMacro.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 345.5 KB
- Last analyzed
- Aug 17, 2026, 10:57 AM UTC
27b856522c1b8972e1b2f65370494d86207fd0fd98b36cf02b4e645ffaeec5d7Safety & 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 WeMacro.exe safe, or is it malware?
What is WeMacro.exe?
How many antivirus engines detected WeMacro.exe?
I already downloaded and ran WeMacro.exe — what should I do?
How do I remove WeMacro.exe?
What is the SHA-256 hash of WeMacro.exe?
How up to date is this analysis of WeMacro.exe?
Community
Member reviews and reports for this exact file hash.