Is Camp_Buddy.exe safe?
No antivirus engine detected malware, but unsigned code, a T1055 runtime mapping, and unresolved direct-IP traffic justify caution before execution.
All 75 antivirus engines were silent, including 17 tier-1 engines, and no known malware family or malicious child was identified. However, one sandbox run mapped possible process injection and recorded direct-IP traffic whose reputation was not checked completely, so execution should be deferred until the file's source is verified.
d98bb399ac0a76101b…6d152b93112dadRecommended 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.
All 75 antivirus engines were silent, including 17 tier-1 engines, and no known malware family or malicious child was identified. However, one sandbox run mapped possible process injection and recorded direct-IP traffic whose reputation was not checked completely, so execution should be deferred until the file's source is verified.
The strongest reassuring evidence is that 0 of 75 engines detected the sample, including all 17 reporting tier-1 engines. Research feeds supplied no known-malware or YARA matches, and the executable does not appear packed or contain high-entropy code. One completed sandbox run nevertheless mapped T1055 and observed direct-IP connections, although it did not produce a malicious sandbox verdict or persistence indicators. Because contacted-host reputation was not saved, those connections cannot be described as benign. The executable is also unsigned, and its two inspected children remain unclassified despite neither being identified as malicious. These mixed findings support caution without establishing a malware family.
What We Detected
None of 75 antivirus engines flagged the executable, including 17 tier-1 engines. No malware family consensus, known-malware intelligence hit, or YARA rule match was present. Static PE inspection found no packer, no high-entropy code, and no brand mismatch, but the executable is unsigned.
Threat Behavior
One sandbox run mapped activity to MITRE T1055, which can represent process injection, and recorded connections to several external IP addresses. The sandbox did not issue a malicious verdict and found no persistence indicators. A complete reputation check for the contacted hosts is unavailable, so the direct-IP traffic remains unresolved. Two dropped files were inspected without a malicious result, but both remain unclassified.
What To Do Now
Verify that the file came from the expected official source and compare its SHA-256 hash with a publisher-provided value if one exists. Keep endpoint protection enabled, and avoid running the file on a production system unless its origin and purpose can be confirmed.
Where this verdict could be wrong4 caveats
- MITRE T1055 was mapped during the single sandbox run, which can indicate process injection even though the exact method and intent were not established.
- The file contacted multiple external IP addresses directly, and contactedHosts=null means no complete host-reputation result is available.
- signing.signed=false for this Win32 executable, so publisher identity and integrity cannot be authenticated.
- similarHashes[0].verdict is suspicious, but matchKind=imphash and signerMatchesSubject=false make that association weak.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/75 antivirus engines detected the file
- All 17 reporting tier-1 engines were undetected
- No malicious sandbox verdict or persistence indicators
- No malicious dropped child identified
- No MalwareBazaar, CIRCL, or YARAify hit
- Unsigned Win32 executable with no authenticated publisher
- Single sandbox run mapped possible process injection to MITRE T1055
- Direct-IP network activity lacks a complete host-reputation check
- Two dropped children remain unclassified
- One imphash-only similar sample previously received a suspicious assessment
Do not execute it until its source and hash are independently verified. Keep endpoint protection enabled and use an isolated environment if further testing is necessary.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial10 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete2 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
- 12MITRE ATT&CK techniques
- 6spawned processes
- 10network contacts
- 36filesystem & 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: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
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.
Moderate concern: Checks which security software you have installed.
Note: Listed running processes; both legitimate software and malware may do this.
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
Camp_Buddy.exe
d98bb399ac0a76101b7a82f8f2b504a3e1d2b38efad7196cd26d152b93112dad
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\program.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\WerFault.exe -u -p 3620 -s 492
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Temp
C:\ProgramData\Microsoft\Windows\WER\Temp
04Isolated runtime analysis - Written fileObserved
406b6847-2643-4f76-a7f8-f7db881766e2
C:\ProgramData\Microsoft\Windows\WER\Temp\406b6847-2643-4f76-a7f8-f7db881766e2
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
13.107.4.52
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
52.251.79.25
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.
- 13.107.4.52
- 52.251.79.25
- 192.168.0.34
- 23.213.37.172
- 23.213.175.32
- 192.168.0.41
- 23.46.228.16
- 20.99.133.109
- 184.27.218.92
- 52.168.117.173
- C:\ProgramData\Microsoft\Windows\WER\Temp
- C:\ProgramData\Microsoft\Windows\WER\Temp\406b6847-2643-4f76-a7f8-f7db881766e2
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue
- C:\ProgramData\Microsoft\Windows\WER\Temp\7bc16320-26fa-4618-b697-4bc57f8c08b6
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERBEDB.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERC7C5.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERCA56.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERBEDB.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERC7C5.tmp.WERInternalMetadata.xml
- Local\WERReportingForProcess3620
- Global\AmiProviderMutex_InventoryApplicationFile
- Global\8d453e4f-d420-4528-9b7b-a67f74bc88eb
- \Sessions\1\BaseNamedObjects\Local\WERReportingForProcess4544
- \Sessions\1\BaseNamedObjects\Global\AmiProviderMutex_InventoryApplicationFile
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache.
- 1bb95b25ca644db96929…a65895Never scannednever seen before
- 07586f204cf7c62b76ce…1b27faNever 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.
- 2rule hits recorded
- 0 / 75engines flagged
- 58sources 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
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 76 times from 58 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Camp_Buddy.exe — d98bb399ac0a76101b7a82f8f2b504a3e1d2b38efad7196cd26d152b93112dad
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\program.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\WerFault.exe -u -p 3620 -s 492
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Temp — C:\ProgramData\Microsoft\Windows\WER\Temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 406b6847-2643-4f76-a7f8-f7db881766e2 — C:\ProgramData\Microsoft\Windows\WER\Temp\406b6847-2643-4f76-a7f8-f7db881766e2
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 13.107.4.52 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 52.251.79.25 — 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.
Evidence"C:\Users\<USER>\Desktop\program.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.
Evidence13.107.4.52 · 52.251.79.25 · 23.213.37.172
0 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
- Camp_Buddy.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 68.5 KB
- Last analyzed
- Sep 23, 2026, 9:00 PM UTC
d98bb399ac0a76101b7a82f8f2b504a3e1d2b38efad7196cd26d152b93112dadSafety & 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 Camp_Buddy.exe safe, or is it malware?
What is Camp_Buddy.exe?
How many antivirus engines detected Camp_Buddy.exe?
I already downloaded and ran Camp_Buddy.exe — what should I do?
How do I remove Camp_Buddy.exe?
What is the SHA-256 hash of Camp_Buddy.exe?
How up to date is this analysis of Camp_Buddy.exe?
Community
Member reviews and reports for this exact file hash.