Is paperline.exe safe?
Signed executable with two low-trust PUP detections, process-injection behaviour, and direct-IP traffic to westbeavers.com.
Two tier-2 engines flag the file as PUP/ApplicUnwnt while 16 tier-1 engines remain silent. Runtime evidence shows process injection (T1055) and direct-IP connections to westbeavers.com, yet no tier-1 consensus or malicious child files exist.
7f1db334fd3302cf98…2b89d02f3d73c3Recommended 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.
Two tier-2 engines flag the file as PUP/ApplicUnwnt while 16 tier-1 engines remain silent. Runtime evidence shows process injection (T1055) and direct-IP connections to westbeavers.com, yet no tier-1 consensus or malicious child files exist.
The file is signed but the signer has no prior history in our database. Two tier-2 engines label it PUP.Optional.XLine and ApplicUnwnt, while the remaining 68 engines report clean. Sandbox data records process injection and direct-IP traffic to four addresses, including westbeavers.com, yet our host-reputation cache contains no malicious entries for those IPs. Prevalence is medium and no similar-hash matches exist, leaving the evidence balanced between a potentially unwanted application and an unknown threat.
What We Detected
75 engines scanned the 7.8 MB Win32 EXE; only Malwarebytes and Xcitium returned malicious labels (PUP.Optional.XLine, ApplicUnwnt). The binary is signed by Guangzhou Guoying Communication Technology Co. with a valid certificate, but the publisher has no historical samples in our records. Sandbox execution captured MITRE techniques T1055 (process injection) and T1562.001 (impair defences) plus direct-IP connections to 104.21.84.219 and related addresses.
Threat Behavior
The sample wrote files under C:\Users\user\AppData\Local\QuartzLine and contacted westbeavers.com endpoints. No dropped children were flagged malicious, and our contacted-host cache returned zero known-bad hosts. Community sandbox reports list a 51/100 score with additional domains such as thankyou.molehawks.com.
What To Do Now
Keep Windows Defender and other endpoint protection enabled. If the file is not required, remove it and monitor for persistence mechanisms. Submit the sample to your security vendor for further classification if you need a definitive verdict.
Where this verdict could be wrong2 caveats
- contactedHosts.inspected=1, maliciousHosts.length=0 — no complete contacted-host reputation result was available in our cache
- droppedChildren.hasMaliciousChild=false — both dropped children returned unknown verdicts
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 16 tier-1 engines reported clean
- No malicious dropped children
- no complete contacted-host reputation result was available contacted
- Process injection capability (T1055)
- Direct-IP network traffic without domain resolution
- Unsigned history for the verified signer
Treat the file as potentially unwanted; remove it unless its origin and purpose are explicitly trusted, and retain endpoint protection.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete2 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 5 contacted hosts were cross-checked; coverage is incomplete.
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
- 10MITRE ATT&CK techniques
- 2spawned processes
- 6network contacts
- 3filesystem & 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: Used an input-capture technique that can record credentials or keystrokes.
High concern: Attempted to impair or bypass security controls.
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.
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
paperline.exe
7f1db334fd3302cf98dd4afddf6f90e98e2a496fe7e86bf1832b89d02f3d73c3
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\quartzline.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\quartzline.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
terrain.dat
C:\Users\<USER>\AppData\Local\QuartzLine\terrain.dat
04Isolated runtime analysis - Written fileObserved
QuartzLine
C:\Users\user\AppData\Local\QuartzLine
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
104.21.84.219
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
172.67.197.98
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.21.84.219
- 172.67.197.98
- 104.21.80.21
- 162.159.36.2
- https://westbeavers.com/quarry/vein
- https://westbeavers.com/quarry/deposit
- C:\Users\<USER>\AppData\Local\QuartzLine\terrain.dat
- C:\Users\user\AppData\Local\QuartzLine
- C:\Users\user\AppData\Local\QuartzLine\terrain.dat
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache.
- 5caa4b6dc05d2efe226c…ed4cdcNever scannednever seen before
- 99a1545acc58b8fe8389…932feaNever 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
- 2 / 75engines flagged
- 8sources 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
2 of 75 antivirus engines flagged the file, including Malwarebytes and Xcitium.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The file has a valid code signature from Guangzhou Guoying Communication Technology Co..
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: paperline.exe — 7f1db334fd3302cf98dd4afddf6f90e98e2a496fe7e86bf1832b89d02f3d73c3
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\quartzline.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\user\Desktop\quartzline.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: terrain.dat — C:\Users\<USER>\AppData\Local\QuartzLine\terrain.dat
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: QuartzLine — C:\Users\user\AppData\Local\QuartzLine
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 104.21.84.219 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 172.67.197.98 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
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\quartzline.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.
Evidence104.21.84.219 · 172.67.197.98 · 104.21.80.21
2 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
- paperline.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Guangzhou Guoying Communication Technology Co.
- Size
- 7.5 MB
- Last analyzed
- Aug 30, 2026, 2:59 PM UTC
7f1db334fd3302cf98dd4afddf6f90e98e2a496fe7e86bf1832b89d02f3d73c3Safety & 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 paperline.exe safe, or is it malware?
What is paperline.exe?
How many antivirus engines detected paperline.exe?
What should I do if I already ran paperline.exe?
How do I remove paperline.exe?
What kind of malware is paperline.exe?
Is paperline.exe digitally signed?
What is the SHA-256 hash of paperline.exe?
How up to date is this analysis of paperline.exe?
Community
Member reviews and reports for this exact file hash.