Is TechnicLauncherBootstrap.exe safe?
Generic detections and concerning LSASS and process-injection indicators warrant caution, although tier-1 engines, host reputation checks, and external intelligence provide substantial counter-evidence.
Six of 75 engines raised generic or grayware-oriented detections, while all 17 reporting tier-1 engines remained silent. Runtime evidence includes process-injection and LSASS-access indicators, but no malicious sandbox verdict, hostile contacted host, malicious child, or researcher-intelligence match corroborates a specific malware family.
bf2b3b934281670142…2917222b5ce975Recommended 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.
Six of 75 engines raised generic or grayware-oriented detections, while all 17 reporting tier-1 engines remained silent. Runtime evidence includes process-injection and LSASS-access indicators, but no malicious sandbox verdict, hostile contacted host, malicious child, or researcher-intelligence match corroborates a specific malware family.
The engine result is mixed: 6 of 75 engines flagged the executable, but none of the 17 reporting tier-1 engines did, and there is no family consensus. One completed sandbox run recorded T1055, T1485, and T1548, with a heuristic also indicating possible LSASS access; these are material concerns but do not establish intent or a specific family. The observed URL hosts were all covered by the saved reputation check, with no malicious or suspicious host result, and the sandbox issued no malicious verdict. The executable is unsigned and has no publisher history, leaving fewer trust anchors than expected for distributed launcher software. Similar-file history trends concerning, but those records share only an imphash without a signer match and therefore may reflect a common installer framework rather than a common payload.
What We Detected
Six of 75 antivirus engines flagged the executable. Kingsoft used a Malgent label, Skyhigh reported behavior resembling an obfuscated executable, Gridinsoft used a generic trojan label, and CrowdStrike reported grayware confidence; however, none of the 17 reporting tier-1 engines identified a threat, and no consistent family emerged.
Threat Behavior
One completed sandbox run mapped activity to T1055, T1485, and T1548. A saved heuristic also indicated activity targeting LSASS, which can be associated with credential access, but the sandbox did not issue a malicious verdict. The four distinct URL hosts were fully represented in the saved host-reputation check, with no malicious or suspicious results; ten dropped files were inspected without a malicious child, although their individual verdicts remain unknown.
What To Do Now
Do not run this copy on a production or sensitive system until its origin and hash are verified through the launcher's official distribution channel. Keep endpoint protection enabled, quarantine the file if its source is uncertain, and use an isolated test environment if further execution analysis is required.
Where this verdict could be wrong4 caveats
- All 17 reporting tier-1 engines, including Avast, BitDefender, ESET-NOD32, Kaspersky, and Fortinet, left the sample undetected.
- behaviour.hasMaliciousSandboxVerdict=false, and the observed URLs point to api.adoptium.net, github.com, release-assets.githubusercontent.com, and launcher.technicpack.net rather than cached hostile infrastructure.
- externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false; these absences reduce corroboration but do not invalidate the runtime concerns.
- droppedChildren inspected 10 hashes without a malicious result, but each child verdict is unknown rather than affirmatively clean.
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 tier-1 detections among 17 reporting tier-1 engines
- No malicious sandbox verdict
- All four distinct observed URL hosts covered with no malicious or suspicious reputation result
- No malicious child among 10 inspected dropped files
- No CIRCL, MalwareBazaar, or YARAify match
- Unsigned Windows executable with no verified publisher history
- Runtime mapping to T1055 process injection
- Heuristic evidence of LSASS-targeting activity
- Additional offensive-technique mappings T1485 and T1548
- Six generic or grayware detections among 75 engines
Verify SHA-256 bf2b3b934281670142852bb42cf77a0c00f39c2696121da5f72917222b5ce975 against the official publisher's release before use. Keep endpoint protection enabled and avoid execution if the download source or hash cannot be confirmed.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete6 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial4 of 10 contacted hosts were cross-checked; coverage is incomplete.
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
- 15MITRE ATT&CK techniques
- 15spawned processes
- 10network contacts
- 40filesystem & 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.
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.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Note: Reads your Windows user-account details.
Note: Collects details about your system.
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
TechnicLauncherBootstrap.exe
bf2b3b934281670142852bb42cf77a0c00f39c2696121da5f72917222b5ce975
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\program.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-KUMC36TE5S.tmp\program.tmp" /SL5="$40188,950272,950272,C:\Users\<USER>\Desktop\program.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
program.tmp
C:\Users\<USER>\AppData\Local\Temp\is-KUMC36TE5S.tmp\program.tmp
04Isolated runtime analysis - Written fileObserved
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-5PG10O8H0S.tmp\_isetup\_setup64.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
104.18.21.66
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
140.82.112.3
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.
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.
- 104.18.21.66
- 140.82.112.3
- 185.199.110.133
- 40.160.33.253
- 104.18.20.66
- 140.82.112.4
- https://api.adoptium.net/v3/binary/latest/25/ga/windows/x64/jre/hotspot/normal/eclipse?project=jdk
- https://github.com/adoptium/temurin25-binaries/releases/download/jdk-25.0.2%2B10/OpenJDK25U-jre_x64_windows_hotspot_25.0.2_10.zip
- https://release-assets.githubusercontent.com/github-production-release-asset/901810329/8516459b-4c0e-49df-a7b5-d060f4cb3e8e?sp=r&sv=2018-11-09&sr=b&spr=https&se=2026-03-28T02%3A39%3A39Z&rscd=attachment%3B+filename%3DOpenJDK25U-jre_x64_windows_hotspot_25.0.2_10.zip&rsct=application%2Foctet-stream&skoid=96c2d410-5711-43a1-aedd-ab1947aa7ab0&sktid=398a6654-997b-47e9-b12b-9515b896b4de&skt=2026-03-28T01%3A39%3A24Z&ske=2026-03-28T02%3A39%3A39Z&sks=b&skv=2018-11-09&sig=1rFCJwDIliIOpRJs5cDCUKYdHnz45NLSQFiGkRPHLfs%3D&jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmVsZWFzZS1hc3NldHMuZ2l0aHVidXNlcmNvbnRlbnQuY29tIiwia2V5Ijoia2V5MSIsImV4cCI6MTc3NDY2Mzc4MiwibmJmIjoxNzc0NjYxOTgyLCJwYXRoIjoicmVsZWFzZWFzc2V0cHJvZHVjdGlvbi5ibG9iLmNvcmUud2luZG93cy5uZXQifQ.CifyHIB2yNS_zukUmwwpn2Qz66UiBFIAhBa1tVsI-c8&response-content-disposition=attachment%3B%20filename%3DOpenJDK25U-jre_x64_windows_hotspot_25.0.2_10.zip&response-content-type=application%2Foctet-stream
- https://launcher.technicpack.net/launcher4/stable/TechnicLauncher.exe
- C:\Users\<USER>\AppData\Local\Temp\is-KUMC36TE5S.tmp\program.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-5PG10O8H0S.tmp\_isetup\_setup64.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-5PG10O8H0S.tmp\_isetup\_is7z.dll
- 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\Temp\is-5PG10O8H0S.tmp\launcher-runtime-extracted
- C:\Users\<USER>\AppData\Local\Temp\is-5PG10O8H0S.tmp\launcher-runtime-staging
- C:\Users\<USER>\AppData\Roaming\.technic\launcher-runtime-staging
- C:\Users\<USER>\AppData\Roaming\.technic\launcher.exe.staging
- C:\Users\<USER>\AppData\Roaming\.technic\launcher-runtime-previous
- cversions.3.m
- \Sessions\1\BaseNamedObjects\Local\RstrMgr3887CAB8-533F-4C85-B0DC-3E5639F8D511
- \Sessions\1\BaseNamedObjects\Local\RstrMgr-3887CAB8-533F-4C85-B0DC-3E5639F8D511-Session0000
- \Sessions\1\BaseNamedObjects\Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:iconcache_idx.db!rwWriterMutex
- \Sessions\1\BaseNamedObjects\Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:iconcache_16.db!dfMaintainer
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 3faf989787b4263d4b39…f28bd2Never scannednever seen before
- 35569fc533d5d814bf5f…6c4606Never scannednever seen before
- ba3065b8fc9b6d1ef507…6996fcNever scannednever seen before
- 3d441136f153b935f624…d07756Never scannednever seen before
- 7739e188e1b179007fe0…51a9f2Never scannednever seen before
- 713642850be4d0ce80a7…4aca57Never scannednever seen before
- 659931b0a68cc61acb90…c29714Never scannednever seen before
- fb4e7cd2c23b70c7164e…164b1eNever scannednever seen before
- 388a796580234efc95f3…136f95Never scannednever seen before
- f97cda058bfe97a7e9ce…06806dNever 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
- 6 / 75engines flagged
- 891sources 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
6 of 75 antivirus engines flagged the file, including APEX and CrowdStrike.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 1,069 times from 891 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: TechnicLauncherBootstrap.exe — bf2b3b934281670142852bb42cf77a0c00f39c2696121da5f72917222b5ce975
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\program.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-KUMC36TE5S.tmp\program.tmp" /SL5="$40188,950272,950272,C:\Users\<USER>\Desktop\program.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: program.tmp — C:\Users\<USER>\AppData\Local\Temp\is-KUMC36TE5S.tmp\program.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _setup64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-5PG10O8H0S.tmp\_isetup\_setup64.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 104.18.21.66 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 140.82.112.3 — 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.
EvidenceC:\Windows\Explorer.EXESandbox 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.
Evidence104.18.21.66 · 140.82.112.3 · 185.199.110.133
6 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
- TechnicLauncherBootstrap.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 2.5 MB
- Last analyzed
- Sep 13, 2026, 7:12 PM UTC
bf2b3b934281670142852bb42cf77a0c00f39c2696121da5f72917222b5ce975Safety & 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 TechnicLauncherBootstrap.exe safe, or is it malware?
What is TechnicLauncherBootstrap.exe?
How many antivirus engines detected TechnicLauncherBootstrap.exe?
What should I do if I already ran TechnicLauncherBootstrap.exe?
How do I remove TechnicLauncherBootstrap.exe?
What is the SHA-256 hash of TechnicLauncherBootstrap.exe?
How up to date is this analysis of TechnicLauncherBootstrap.exe?
Community
Member reviews and reports for this exact file hash.