File verdict·Decided by the MT AI Engine
Our call

Suspicious

Installer shows process-injection and direct-IP contact signals alongside an imphash tied to OfferCore PUA samples.

offercoreSigned but unverified · BeamMP Mod Team
Trust score42Caution
BeamMP_Installer.exe
4.7 MB
7b216d881d9541cb2caf7bb3e1e2
Antivirus engines
1 of 74 flagged
Code signing
Unverified: BeamMP Mod Team
Age
First seen 3mo ago
MT AI Engine · Verdict analysis

The reasoning behind this verdict

The MT AI Engine weighs every signal from this scan — antivirus detections, sandbox behaviour, code signing, prevalence and historical matches — to reach a single, evidence-based verdict.

65%Confidence
High
Reasoning

The single CrowdStrike detection carries an adwarePua label but lacks tier-1 support. Offensive MITRE techniques T1055, T1485 and T1548 plus three high/medium heuristics indicate suspicious runtime behaviour. Five similar imphash samples were previously classified malicious or suspicious with OfferCore family. YARAify returned eight rules including injection detectors. No malicious dropped children or contacted hosts were found, and the file contacts BeamMP backend domains, leaving the overall picture borderline.

Key signals · 5

Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.

  1. engines.topDetections[0]: CrowdStrike tier2 win/grayware_confidence_60% (D) adwarePua

  2. signing.signer: BeamMP Mod Team with signerStats.found=false

  3. similarHashes[0].verdict: malicious (matchKind=imphash, family=offercore)

  4. triggeredHeuristics[0]: MalwareTips.Synth.ProcessInjection high severity T1055

  5. externalIntel.yaraify.ruleCount=8 with CP_Script_Inject_Detector match

Points in its favour
  • No tier-1 engine detections
  • No malicious dropped children
  • No known-malicious contacted hosts
  • Medium prevalence across thousands of submissions
Points against
  • Process injection (T1055) observed in sandbox
  • Direct-IP C2 pattern without DNS usage
  • Imphash collision with known OfferCore samples
  • YARAify injection and TLS-section rules matched
Recommended action

Treat as suspicious PUA; do not run on production systems until the BeamMP project confirms the binary hash.

What this file does

What it attempted when executed in an isolated sandbox

  • High concern: Hides inside another running program to evade antivirus.

  • High concern: Talks to a remote server to take commands or send out your data.

  • Moderate concern: Obfuscates or packs its code to avoid detection.

  • Moderate concern: Lists running programs — often to find security tools.

  • Moderate concern: Deletes traces of itself to cover its tracks.

  • Moderate concern: Checks whether it's being watched in a sandbox before acting.

  • Moderate concern: Checks which security software you have installed.

Translated from the file's technical behaviour during analysis. It never ran on your device.

What to do now

We couldn't fully clear this file. Treat it with caution.

  1. Don't run it unless you're certain it came from a source you trust.

  2. Check where you got it — an email attachment or a random download link is a red flag.

  3. If you're unsure, delete it. You can always re-download a clean copy from the official source.

  4. If you're still unsure, scan it again in a day or two — detections often catch up on newer files.

Threat family attribution

Borland corroborated by 2 sources

  • 8 YARA rules
    Borland, CP_Script_Inject_Detector, HUNTING_SUSP_TLS_SECTION
  • MT AI Engine
    offercore
Runtime behaviour

What this file did when executed

This file was detonated in 1 sandbox and its runtime behaviour was observed.

MITRE ATT&CK
16

Adversary techniques mapped to the MITRE ATT&CK framework.

T1012T1027· Obfuscated codeT1027.002· Obfuscated codeT1036T1055· Process injectionT1057· Lists programsT1070· Covers its tracksT1071· Remote server (C2)T1082· System reconT1129· Loads modulesT1202T1485T1497· Sandbox evasionT1518· Checks your AVT1548T1573
Spawned processes
14
$(unnamed)
"C:\Users\<USER>\Desktop\BeamMP_Installer.exe"
$(unnamed)
"C:\Users\<USER>\AppData\Local\Temp\is-EKAQ040KCC.tmp\BeamMP_Installer.tmp" /SL5="$70070,3625129,1208320,C:\Users\<USER>\Desktop\BeamMP_Installer.exe"
$(unnamed)
C:\Windows\Explorer.EXE
$(unnamed)
"C:\Users\<USER>\AppData\Roaming\BeamMP-Launcher\BeamMP-Launcher.exe"
$(unnamed)
C:\Windows\system32\cmd.exe /c cls
$(unnamed)
C:\Windows\system32\services.exe
$(unnamed)
C:\Windows\System32\svchost.exe -k NetworkService -p
$(unnamed)
C:\Windows\system32\svchost.exe -k UnistackSvcGroup
+6 more processes captured.
Network activity
7
IP addresses3
  • 104.21.24.118
  • 3.163.189.62
  • 162.159.36.2
URLs4
  • http://crls.ssl.com/SSLcom-TLS-Root-2022-ECC.crl
  • http://crls.ssl.com/SSL.com-TLS-T-ECC-R2.crl
  • https://backend.beammp.com/sha/launcher?branch=&pk=
  • https://backend.beammp.com/version/launcher?branch=&pk=
Filesystem & mutexes
27
Files written15
  • C:\Users\<USER>\AppData\Local\Temp\is-EKAQ040KCC.tmp\BeamMP_Installer.tmp
  • C:\Users\<USER>\AppData\Local\Temp\is-82HO9YQRRN.tmp\_isetup\_setup64.tmp
  • C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_idx.db
  • C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_256.db
  • C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_48.db
+10 more
Files deleted11
  • C:\Users\<USER>\AppData\Roaming\BeamMP-Launcher\is-KACI0FVEUF.tmp
  • C:\Users\<USER>\AppData\Roaming\BeamMP-Launcher\is-6NRWQCJPBR.tmp
  • C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\BeamMP-Launcher\BeamMP-Launcher.lnk
  • C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\BeamMP-Launcher\BeamMP-Launcher.pif
  • C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\BeamMP-Launcher\BeamMP-Launcher.url
+6 more
Mutexes created1
  • cversions.3.m
Dropped payload

Files this sample writes at runtime

This file drops 10 children at runtime. None are currently flagged malicious in our cache.

10 unseen
  • 1c53f0cfaf81df0e3cb8d5a768Never scanned
    never seen before
  • 314f99e2316ca296d3db7a3683Never scanned
    never seen before
  • f65e7f4431506c25813827289dNever scanned
    never seen before
  • b8996632026de2da49ae15e4e8Never scanned
    never seen before
  • 35569fc533d5d814bf5f6c4606Never scanned
    never seen before
  • a0160f0c7c32954339ad1f125eNever scanned
    never seen before
  • 2354b257fdbed9193c43e4be96Never scanned
    never seen before
  • 388a796580234efc95f3136f95Never scanned
    never seen before
  • 35a74b3ec25677d8ae6088a2edNever scanned
    never seen before
  • 659931b0a68cc61acb90c29714Never scanned
    never seen before
External threat intelligence

1 corroborating signal from researcher-curated sources

YARAify HIT·8 community rules matchedView on YARAify
  • Borlandby malware-lu
  • CP_Script_Inject_Detectorby DiegoAnalytics
    Detects attempts to inject code into another process across PE, ELF, Mach-O binaries
  • HUNTING_SUSP_TLS_SECTIONby chaosphere
    Detect PE files with .tls section that can be used for anti-debugging
  • pe_detect_tls_callbacks
  • PE_Digital_Certificateby albertzsigovits
Cross-referenced against MalwareBazaar (abuse.ch), YARAify, and the CIRCL hashlookup reference DB.
Signature matches

YARA & heuristic rule matches

A researcher-curated or high-severity heuristic rule matched this sample. These rules target specific malware families and are near-definitive.

5 YARAify3 synthesis
MITRE ATT&CK profile
Defense evasion× 1Cred access× 1C2× 1
YARAify (community)
Researcher-authored rules via abuse.ch
  • Borland
  • CP_Script_Inject_Detector
  • HUNTING_SUSP_TLS_SECTION
  • pe_detect_tls_callbacks
  • PE_Digital_Certificate
MalwareTips synthesis rules
Our own detection rules, applied to the scan data and sandbox behaviour
  • ProcessInjectionhigh

    MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.

    Evidence
    C:\Windows\Explorer.EXE
  • CredentialDumpermedium

    Sandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.

    Evidence
    C:\Windows\system32\lsass.exe
  • DirectIpC2medium

    Sample contacted 3 external IP address(es) and zero domains. Benign software virtually always uses DNS; no-DNS direct-IP C2 is a strong malware indicator because it bypasses reputation systems and dodges domain-based blocklists.

    Evidence
    104.21.24.118 · 3.163.189.62 · 162.159.36.2
Antivirus engine breakdown

1 detection across 74 engines

1 malicious0 suspicious73 clean
Tier-117 engines
0flag
Top commercial AVs (low FP rate)
Tier-240 engines
1flag
Mainstream engines with mixed FP rates
Low-trust17 engines
0flag
Heuristic / generic-AI engines (high FP rate)
CrowdStrike
malicious
win/grayware_confidence_60% (D)
Hash 7b216d881d95… cross-referenced against 74 AV engines via our AV network.
PE forensics

Section entropy & packers

Section-level entropy and packer detection from the PE header. Nothing suspicious here — entropy is within the normal range for unpacked code.

ent 8.00Unpacked
Section entropy10 sections
.text
6.38
.itext
6.04
.data
5.18
.bss
0.00
.idata
4.82
.didata
2.76
.edata
1.34
.tls
0.00
.rdata
1.38
.reloc
6.70
0.0Packed threshold 7.28.0
Prevalence

How widely this file has been seen

Moderate prevalence — neither rare nor common. No strong prior applies.

Medium
Unique uploaders
2,988
Hundreds of people have uploaded this — common.
Total submissions
4,155
Includes repeat uploads by the same source.
First seen
3mo ago
Apr 12, 2026
Prevalence quadrant
Rare · New
Targeted malware lives here
Common · New
Just-released software
Rare · Old
Niche or internal tooling
Common · Old
Trusted legitimate binaries
File identity

Forensic fingerprint

File biography
First seen (VT)
4/12/2026, 7:56:32 PM
First seen (MalwareBazaar)
Last analysis (VT)
7/18/2026, 6:51:38 PM
Scanned here
7/19/2026, 6:07:08 AM
File name
BeamMP_Installer.exe
Size
4.70 MB
MIME type
(unknown)
Detected type
Win32 EXE
SHA-256
7b216d881d9541cb2c563393963cccedf4c55d3282aa30abb39585af7bb3e1e2
MD5
8b6ef9a77a5bc84734c3995ec4ebf6b3
SHA-1
3e9ca457715c5ab585a286dd2233b0d21a199b79
PE imphash
88016fcdef7f227c62171d0afad9aae4
First seen (VT)
4/12/2026, 7:56:32 PM
Last analysis (VT)
7/18/2026, 6:51:38 PM
First scan (MalwareTips)
7/19/2026, 6:07:08 AM
Last scan (MalwareTips)
7/19/2026, 6:07:08 AM
Code signer
BeamMP Mod Teaminvalid
Community reputation
+1trusted
Behavior tags
peexesignedoverlayinvalid-signature
Frequently asked

Safety FAQ

Common questions about BeamMP_Installer.exe, answered from the scan data above.

  • BeamMP_Installer.exe is suspicious — treat it as unsafe until you're sure. 1 of 74 antivirus engines flag it (family: offercore), which isn't a strong consensus but is enough to be cautious. Don't run it unless you fully trust where it came from, and prefer downloading the software fresh from its official site.
  • BeamMP_Installer.exe is a Windows executable program, about 4.7 MB. We identify a file by its cryptographic hash rather than its name, because the same filename can be reused by completely different files — the hash below is the reliable fingerprint.
  • 1 of 74 antivirus engines flagged BeamMP_Installer.exe, 1 of them as outright malicious. A small number of detections can include false positives, so we weigh which engines flagged it and what else the file does, not just the raw count.
  • 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 BeamMP_Installer.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 the original BeamMP_Installer.exe file and empty the Recycle Bin/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.
  • BeamMP_Installer.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.
  • BeamMP_Installer.exe claims a signer of BeamMP Mod Team, but the signature is not verified — an unverified or broken signature can be forged, so it should not be trusted as proof of who made the file.
  • The SHA-256 hash of BeamMP_Installer.exe is 7b216d881d9541cb2c563393963cccedf4c55d3282aa30abb39585af7bb3e1e2, and its MD5 is 8b6ef9a77a5bc84734c3995ec4ebf6b3. 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 19, 2026. Because a file's hash never changes, the identity of BeamMP_Installer.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.
Community classification

Reviews & malware reports(0)

Tell the community what you saw. Tag the sample — Trojan, Adware, False Positive — and share what the file did on your system. Your report helps confirm or dispute the AV verdict.

Loading…
Loading reports…
Files are processed in a streaming pass-through — MalwareTips never stores the binary on its servers. Only the scan result (hash, detections, verdict) is retained so the next person who scans the same file gets an instant answer. If you ran this file on your computer and are worried, scan your system with an up-to-date antivirus and change critical passwords from a different device.