Is macroB.exe safe?
Unsigned 11 MB PE with tier-2 detections, process-injection and LSASS access in sandbox, mixed imphash history.
Four of 75 engines flagged the file; three tier-2 detections cite dropper-like behaviour. Sandbox recorded process injection and LSASS access, yet no tier-1 consensus or malicious children. Similar imphash files show mixed verdicts.
577b4923723acc2526…742e2d0cfb9f27Recommended 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.
Four of 75 engines flagged the file; three tier-2 detections cite dropper-like behaviour. Sandbox recorded process injection and LSASS access, yet no tier-1 consensus or malicious children. Similar imphash files show mixed verdicts.
The file is unsigned and triggers two high-severity MITRE techniques in a single sandbox run. Three tier-2 engines label it malicious while tier-1 engines remain silent. Prior imphash matches include two malicious and two suspicious verdicts, preventing a clean or malicious consensus. Medium prevalence and absence of malicious dropped children keep the risk moderate.
What We Detected
Four engines out of 75 flagged macroB.exe. DeepInstinct, SentinelOne and Skyhigh (tier-2) reported malicious or suspicious behaviour; one low-trust engine also flagged it. No tier-1 engine raised an alert and no family consensus exists.
Threat Behavior
Sandbox execution showed process injection (T1055) and data-encryption activity (T1486), plus access to LSASS. The sample wrote ten temporary files, none of which were later flagged malicious. One direct-IP connection was observed; host reputation data is unavailable.
What To Do Now
Do not execute the file. Keep endpoint protection enabled. If the file is required for legitimate work, run it only in an isolated virtual machine and monitor for unexpected outbound traffic or new processes.
Where this verdict could be wrong2 caveats
- droppedChildren.hasMaliciousChild=false and 10 children inspected with no malicious verdicts
- behaviour.hasMaliciousSandboxVerdict=false despite offensive MITRE techniques
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 tier-1 engine detections
- No malicious dropped children
- Medium prevalence over 160 days
- Unsigned executable
- Process injection observed in sandbox
- LSASS access (credential-store targeting)
- Two prior imphash matches flagged malicious
Treat the sample as suspicious; isolate and analyse further before any execution on production systems.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete4 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete3 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
- 14MITRE ATT&CK techniques
- 9spawned processes
- 1network contacts
- 15filesystem & 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: Encrypted files or data, behaviour commonly associated with ransomware.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
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.
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
macroB.exe
577b4923723acc2526b48d163513e4256a41708c7118f2a15d742e2d0cfb9f27
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\program.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\cmd.exe /c "ver"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
VCRUNTIME140.dll
C:\Users\<USER>\AppData\Local\Temp\_MEI28002\VCRUNTIME140.dll
04Isolated runtime analysis - Written fileObserved
VCRUNTIME140_1.dll
C:\Users\<USER>\AppData\Local\Temp\_MEI28002\VCRUNTIME140_1.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
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.
- 162.159.36.2
- C:\Users\<USER>\AppData\Local\Temp\_MEI28002\VCRUNTIME140.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI28002\VCRUNTIME140_1.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI28002\_bz2.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI28002\_ctypes.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI28002\_decimal.pyd
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 48f4a239c25354f0e9f8…17ecedNever scannednever seen before
- 3271d39d7b4dcd841e8e…efe5e5Never scannednever seen before
- cb71909bf01a3a7a4c73…d46e13Never scannednever seen before
- 6a99bc0128e0c7d6cbbf…cbc6c8Never scannednever seen before
- 98074c85650a420a095a…b084e9Never scannednever seen before
- 81eca6840b87f2def9fc…d7aaaaNever scannednever seen before
- 4f05f31ca026bbfeeee4…7ab5deNever scannednever seen before
- 3130bf26da0c840c1e02…5a3539Never scannednever seen before
- 47576cae321c80e69c7f…ac6b91Never scannednever seen before
- 165be658ab7d61ffc3df…d3acd7Never 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.
- 3rule hits recorded
- 4 / 75engines flagged
- 45sources 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
4 of 75 antivirus engines flagged the file, including APEX and DeepInstinct.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 54 times from 45 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: macroB.exe — 577b4923723acc2526b48d163513e4256a41708c7118f2a15d742e2d0cfb9f27
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\program.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\cmd.exe /c "ver"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: VCRUNTIME140.dll — C:\Users\<USER>\AppData\Local\Temp\_MEI28002\VCRUNTIME140.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: VCRUNTIME140_1.dll — C:\Users\<USER>\AppData\Local\Temp\_MEI28002\VCRUNTIME140_1.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — Contact observed during runtime.
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.exeThe 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.
Evidence162.159.36.2
4 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
- macroB.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 10.5 MB
- Last analyzed
- Aug 13, 2026, 9:20 PM UTC
577b4923723acc2526b48d163513e4256a41708c7118f2a15d742e2d0cfb9f27Safety & 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 macroB.exe safe, or is it malware?
What is macroB.exe?
How many antivirus engines detected macroB.exe?
I already downloaded and ran macroB.exe — what should I do?
How do I remove macroB.exe?
What kind of malware is macroB.exe?
What is the SHA-256 hash of macroB.exe?
How up to date is this analysis of macroB.exe?
Community
Member reviews and reports for this exact file hash.