Our call: Is Battlefield 4_QhLY2-6.exe safe?Malicious
21 of 74 engines flag this OfferCore bundler with tier-1 consensus and matching malicious imphash history.
- 1 high-confidence signature or behavior rule matched this file.Derived · Signature and behavior rules
- 21 of 74 antivirus engines flagged the file, including AhnLab-V3 and ALYac.Observed · Antivirus analysis
- The file has a valid code signature from Infivora.Observed · Code-signing metadata
aa27557ece7ea88672…7e08e4fc89Recommended 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.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete21 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial12 of 32 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete2 signature or behavior rules 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
Battlefield 4_QhLY2-6.exe
aa27557ece7ea88672c2c0ef89b2bfdf2c7dbfb54219530184c6b07e08e4fc89
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\Battlefield 4_QhLY2-6.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-AHB1HNROHY.tmp\Battlefield 4_QhLY2-6.tmp" /SL5="$6014A,14880881,843264,C:\Users\<USER>\Desktop\Battlefield 4_QhLY2-6.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Battlefield 4_QhLY2-6.tmp
C:\Users\<USER>\AppData\Local\Temp\is-AHB1HNROHY.tmp\Battlefield 4_QhLY2-6.tmp
04Isolated runtime analysis - Written fileObserved
$Quota:$Q:$INDEX_ALLOCATION
C:\$Extend\$Quota:$Q:$INDEX_ALLOCATION
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
3.167.161.39
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
52.85.12.49
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
21 of 74 antivirus engines flagged the file, including AhnLab-V3 and ALYac.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The file has a valid code signature from Infivora.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: Battlefield 4_QhLY2-6.exe — aa27557ece7ea88672c2c0ef89b2bfdf2c7dbfb54219530184c6b07e08e4fc89
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\Battlefield 4_QhLY2-6.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-AHB1HNROHY.tmp\Battlefield 4_QhLY2-6.tmp" /SL5="$6014A,14880881,843264,C:\Users\<USER>\Desktop\Battlefield 4_QhLY2-6.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Battlefield 4_QhLY2-6.tmp — C:\Users\<USER>\AppData\Local\Temp\is-AHB1HNROHY.tmp\Battlefield 4_QhLY2-6.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: $Quota:$Q:$INDEX_ALLOCATION — C:\$Extend\$Quota:$Q:$INDEX_ALLOCATION
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 3.167.161.39 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 52.85.12.49 — 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.
Six tier-1 engines plus multiple tier-2 detections converge on the OfferCore family; the Infivora-signed sample shows process-injection behaviour and direct-IP traffic. Five prior imphash matches were all classified malicious.
The engine consensus is decisive: tier1Malicious=6 with a named family and consistent OfferCore labels across vendors. The signer has a 100 % malicious history on its single prior sample, and the imphash matches five earlier OfferCore samples that received malicious verdicts. Observed T1055 process injection and direct-IP connections without domains add behavioural weight. Although sandbox and host-reputation checks returned no explicit malicious verdict, the static and engine evidence outweighs those neutral signals.
What We Detected
21 of 74 engines flagged the file, including six tier-1 engines (Avast, AVG, BitDefender, DrWeb, Emsisoft, ESET-NOD32, Fortinet, GData, Microsoft) that label it OfferCore or FileRepMalware. The sample is signed by Infivora, a publisher whose only prior submission was malicious. Five similar files sharing the same imphash were previously classified malicious under the OfferCore family.
Threat Behavior
Runtime evidence shows process-injection activity (MITRE T1055) and direct-IP connections to 15 addresses without domain names. The installer writes temporary files and spawns child processes typical of bundlers that drop additional payloads. No malicious child files or known-bad hosts were confirmed in the available data.
What To Do Now
Do not execute the file. If it was downloaded from an untrusted source, delete it and scan the system with up-to-date endpoint protection. Keep security software enabled; disabling protection increases exposure to similar bundlers.
Where this verdict could be wrong3 caveats
- contactedHosts.maliciousHosts.length=0 and droppedChildren.hasMaliciousChild=false — no confirmed malicious network or child activity observed.
- behaviour.hasMaliciousSandboxVerdict=false — sandbox did not return an explicit malicious verdict despite T1055 mapping.
- prevalence.classification=medium — file is not rare_new, reducing likelihood of a brand-new unknown threat.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- contactedHosts.maliciousHosts.length=0
- droppedChildren.hasMaliciousChild=false
- behaviour.hasMaliciousSandboxVerdict=false
- tier1Malicious=6 with OfferCore family consensus
- signer Infivora has 100% malicious history
- T1055 process injection observed
- direct-IP traffic without domains
- imphash matches five prior malicious OfferCore samples
Treat the file as malicious; remove it and avoid executing similar OfferCore-signed installers.
Behavior
Plain-English impact first, then the observed runtime evidence.
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal 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.
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.
Threat context
How bundlers & adware work
This is a bundler — a real-looking installer that hides extra software inside. When you run it, it quietly installs things you never asked for: ad injectors, browser toolbars, fake 'PC cleaner' apps, or even more bundlers. The people behind it get paid for every unwanted app they sneak on.
Bottom line:It's not usually built to destroy files, but it slows your PC, floods it with ads, and can be a real pain to fully remove.
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.
- 3.167.161.39
- 52.85.12.49
- 161.69.237.46
- 23.192.220.209
- 161.69.232.147
- 107.167.125.189
- 107.167.96.44
- 104.18.24.17
- 18.160.249.42
- 3.167.183.123
- http://statusd.digitalcertvalidation.com/MFEwTzBNMEswSTAJBgUrDgMCGgUABBRNolijWxrE%2B4oss3hMFE8Heagz1AQU9VYiH9m%2Fa1kkUrDhas3A4Vdn6egCEAaV2Cvjf8%2BY2vZ6CGdVSuk%3D
- https://d2cxzkcwhivupa.cloudfront.net/o
- https://d2cxzkcwhivupa.cloudfront.net/zbd
- https://d2cxzkcwhivupa.cloudfront.net/f/RAV_Triple_NCB/images/DOTPS-855/EN.png
- https://d2cxzkcwhivupa.cloudfront.net/f/WebAdvisor/images/NEW/EN.png
- https://d2cxzkcwhivupa.cloudfront.net/f/OperaGX/images/DOTPS-1867/LightBG/EN.png
- C:\Users\<USER>\AppData\Local\Temp\is-AHB1HNROHY.tmp\Battlefield 4_QhLY2-6.tmp
- C:\$Extend\$Quota:$Q:$INDEX_ALLOCATION
- C:\Users\<USER>\AppData\Local\Temp\is-OMZ4VK04CT.tmp\Battlefield 4_QhLY2-6.tmp
- C:\Users\user\AppData\Local\Temp\is-1YK4ZL6767.tmp
- C:\Users\user\AppData\Local\Temp\is-1YK4ZL6767.tmp\Battlefield 4_QhLY2-6.tmp
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache.
- dc8c86bf2ce73f88cf48…ecf0f3Never scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Detection sources at a glance
Category: pua
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\Battlefield 4_QhLY2-6.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.
Evidence3.167.161.39 · 52.85.12.49 · 161.69.237.46
21 of 74 engines flagged this file
View all 74 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
- Battlefield 4_QhLY2-6.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Infivora
- Size
- 15.4 MB
- Last analyzed
- Jul 25, 2026, 2:30 PM UTC
aa27557ece7ea88672c2c0ef89b2bfdf2c7dbfb54219530184c6b07e08e4fc89Safety & 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.
Don't run this file. Delete this file from the device, then empty the Recycle Bin or Trash.
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.
If you typed any passwords while it was open, change them from a device you trust.
Get a fresh copy from the developer's official site or an official app store.
Safety FAQ
- Yes — Battlefield 4_QhLY2-6.exe is malicious. Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash. 21 of 74 antivirus engines flag it (family: offercore). It behaves as adware or a potentially unwanted program (PUA) — not always destructive, but it bundles ads, trackers, or unwanted changes you didn't ask for. If you've already run it, see the removal and recovery steps below.
- Battlefield 4_QhLY2-6.exe is a Windows executable program (application/x-msdownload), about 15.4 MB. Our analysis identifies it as malicious (family: offercore) — adware or a potentially unwanted program (PUA) — not always destructive, but it bundles ads, trackers, or unwanted changes you didn't ask for. Because a file's name and icon can be faked, the safest way to identify it is by its cryptographic hash (below), not its filename.
- 21 of 74 antivirus engines flagged Battlefield 4_QhLY2-6.exe, 21 of them as outright malicious. The raw count alone does not establish safety or danger; we also weigh which engines flagged it and corroborating behavior, identity, reputation, and rule evidence. The malicious verdict comes from the complete saved evidence, not from this antivirus count by itself.
- Act quickly. 1) Disconnect the device from the internet to stop the malware communicating or spreading. 2) Run a full scan with reputable anti-malware software (such as Malwarebytes) and quarantine everything it finds. 3) Change your important passwords from a DIFFERENT, clean device — many threats log keystrokes or steal saved credentials. 4) If you bank or shop on this device, watch closely for fraud and alert your bank. 5) For a confirmed infection, the most reliable fix is to back up your personal files and reinstall the operating system for a clean start.
- To remove Battlefield 4_QhLY2-6.exe: 1) restart into Safe Mode (Safe Mode with Networking if you need to download a tool) so the malware doesn't auto-start. 2) Run a full scan with reputable anti-malware software and let it quarantine or delete the detections. 3) Delete this file from the device, then empty the Recycle Bin or Trash. 4) Check your browser extensions, startup items, and scheduled tasks for anything unfamiliar. 5) Reboot and scan again to confirm it's gone. If detections keep coming back, a clean operating-system reinstall is the most dependable cure.
- Battlefield 4_QhLY2-6.exe is classified as adware or a potentially unwanted program (PUA) — not always destructive, but it bundles ads, trackers, or unwanted changes you didn't ask for. Engines attribute it to the offercore family. Knowing the family matters because it tells you the likely impact — data theft, remote control, file encryption, or unwanted ads — and guides the cleanup.
- Yes — Battlefield 4_QhLY2-6.exe carries a valid digital signature from Infivora, which confirms the file hasn't been tampered with since that publisher signed it. A valid signature is a positive signal, but note that malware is occasionally signed with stolen or abused certificates, so it isn't proof of safety on its own.
- The SHA-256 hash of Battlefield 4_QhLY2-6.exe is aa27557ece7ea88672c2c0ef89b2bfdf2c7dbfb54219530184c6b07e08e4fc89, and its MD5 is b8c1ff193853530327c6e03654b4cb91. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
- This report reflects the scan run on July 25, 2026. Because a file's hash never changes, the identity of Battlefield 4_QhLY2-6.exe is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.