Our call: Is War2PLoader.exe safe?Suspicious
Unsigned 12-year-old EXE with one tier-1 Artemis flag, direct-IP traffic, and a process-injection YARA hit.
- 7 of 76 antivirus engines flagged the file, including APEX and CrowdStrike.Observed · Antivirus analysis
- The hash has been submitted 9 times from 7 sources.Derived · Saved report facts
43d4fabb0880578e66…384467af23Recommended 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.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete7 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial12 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule matched.
External intel
Complete3 of 3 independent reference sources completed.
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
War2PLoader.exe
43d4fabb0880578e66df52a1be48aa0cdf9761f75f639d4af53838384467af23
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
%SAMPLEPATH%\War2PLoader.exe
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\43d4fabb0880578e66df52a1be48aa0cdf9761f75f639d4af53838384467af23.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
192.168.0.71
Contact observed during runtime.
04Isolated runtime analysis - Contacted hostObserved
a83f:8110:cce1:d301:b47e:d5e5:4ef0:d901
Contact observed during runtime.
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.
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
7 of 76 antivirus engines flagged the file, including APEX and CrowdStrike.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 9 times from 7 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: War2PLoader.exe — 43d4fabb0880578e66df52a1be48aa0cdf9761f75f639d4af53838384467af23
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — %SAMPLEPATH%\War2PLoader.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — %SAMPLEPATH%\43d4fabb0880578e66df52a1be48aa0cdf9761f75f639d4af53838384467af23.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Contacted host: 192.168.0.71 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: a83f:8110:cce1:d301:b47e:d5e5:4ef0:d901 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
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.
7 of 76 engines flagged the file, including one tier-1 detection of Artemis. The binary is unsigned, contacted ten raw IPs, and triggered a process-injection heuristic, yet no sandbox verdict or confirmed malicious hosts exist.
The single tier-1 detection and unsigned status create a mixed signal that prevents a clean verdict. Direct-IP traffic and the THOR YARA rule add suspicion, but the absence of sandbox malice, dropped children, and host-reputation data leaves the file in a borderline state. Medium prevalence over twelve years without stronger attribution further supports treating it as suspicious rather than malicious or safe.
What We Detected
One tier-1 engine (McAfee) labels the sample Artemis!BCABB036A8DE; five low-trust engines add generic malicious or grayware tags. The file is an unsigned 122 kB Win32 EXE first seen in 2015.
Threat Behavior
A single sandbox run recorded nine ambient MITRE techniques and ten direct IP contacts with no domain names. The DirectIpC2 heuristic fired, but no malicious sandbox verdict or dropped children were observed. A community YARA rule flags process-injection indicators.
What To Do Now
Do not execute the file. Keep endpoint protection enabled and submit the sample to additional sandboxes for deeper behavioural analysis before any trust decision.
Where this verdict could be wrong3 caveats
- Only one tier-1 engine flagged the sample; the remaining 17 tier-1 engines returned clean.
- No sandbox verdict, no dropped children, no contactedDomains, and contactedHosts cross-check is missing — cannot confirm malicious host contact.
- File is 4162 days old with medium prevalence, suggesting long-term survival without widespread malicious attribution.
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 one tier-1 engine flagged
- no sandbox malice
- medium long-term prevalence
- unsigned executable
- tier-1 Artemis detection
- direct-IP traffic without domains
- process-injection YARA match
Treat the file as untrusted; obtain further sandbox or dynamic-analysis results before any execution or distribution decision.
Behavior
Plain-English impact first, then the observed runtime evidence.
What this file does
Observed actions and their security significance
High concern: Manipulated how the operating system loads code, which can redirect execution.
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.
Note: Inspects your network configuration.
Note: Collects details about your system.
Note: Loads extra code modules while running.
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.
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.
- 192.168.0.71
- a83f:8110:cce1:d301:b47e:d5e5:4ef0:d901
- 20.99.186.246
- 192.229.211.108
- 23.216.147.64
- 192.168.0.42
- 20.99.185.48
- 23.221.103.220
- 23.215.176.19
- 52.185.73.156
- %USERPROFILE%\AppData\Local\Microsoft\Windows\INetCache\IE\KLT1I0ZU\update50[1].xml
- C:\Windows\System32\wbem\Performance\WmiApRpl.h
- C:\Windows\System32\wbem\Performance\WmiApRpl.ini
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
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
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
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.
Evidencea83f:8110:cce1:d301:b47e:d5e5:4ef0:d901 · 20.99.186.246 · 192.229.211.108
7 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- War2PLoader.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 119.5 KB
- Last analyzed
- Jul 31, 2026, 7:56 AM UTC
43d4fabb0880578e66df52a1be48aa0cdf9761f75f639d4af53838384467af23Safety & 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.
Don't run it unless you're certain it came from a source you trust.
Check where you got it — an unexpected attachment or a random download link is a red flag.
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.
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.