YAPA: Analysis of DailyFIle PDF App



In this series of YAPA (Yet Another PDF Application), I continue to document newly observed suspicious PDF converter applications. The latest one is DailyFile, which can be found on dailytapp[.]com. 

Dailytapp Download Page




The above image shows the a similar style to many other observed malicious pdf, document, and zip converter applications.

Analysis:

The analysis of this started by pivoting off of other known indicators, primarily the certificate signer: "Astras Novei LTD" which had also been observed with a malicious python based converter Ziply

Additionally, "A1A Marketing Ltd." had been previously observed with other YAPA sites like pdf-star[.]com and powerdocapp[.]com. We also see "Sherlock Tech Ltd" which points to other YAPA samples as well.

Ads Transparency for dailytapp


This is a .NET application, which makes it easy to load and observe in DnSpy. The YAPA here performs similar functions as previously observed instances. We can see simple obfuscation of "Google and Chrome", we can see infrastructure (Domains/URIs), and we can see a hard coded XOR key intended to obscure network communications.

Obfuscated .NET code


Hard-Coded XOR key



Some new hunting finds based on advertiser and signature pivots include ZipSphere, PDFShark, FreePDFApp, and PDFDoc.

Indicators of Compromise (IOCs)

Type Indicator Description
Domain api.dailytapp.com Primary API endpoint used by the installer for validation, configuration retrieval, and telemetry reporting.
Domain init.dailytapp.com Secondary server used for browser synchronization operations including profile upload and modification.
URI /ValidateDailyFile Validation endpoint contacted during installation to register the client.
URI /CheckEndpoint Returns server-controlled content displayed in the installer interface.
URI /Reporter Telemetry endpoint receiving system information and installation status.
URI /InitDaily Initial configuration endpoint used to retrieve browser synchronization instructions.
URI /Check Endpoint used to upload Chrome profile data and retrieve modified configuration files.
URI /FeReport Reporting endpoint used to log synchronization results.
URI /TaReport Additional telemetry endpoint reporting browser manipulation outcomes.
File Path %LOCALAPPDATA%\DailyFile\DailyFileApp.exe Main application dropped by the installer.
File Path %LOCALAPPDATA%\DailyFile\DailyFileUninstall.exe Uninstall component installed alongside the application.
File Path %LOCALAPPDATA%\DailyFile\PdfSharp.dll Bundled PDF library used to support the application's legitimacy.
File Path %LOCALAPPDATA%\DailyFile\Spire.Doc.dll Bundled document processing library.
File Path %LOCALAPPDATA%\DailyFile\Spire.Pdf.dll Bundled PDF processing library.
Registry Key HKCU\SOFTWARE\DailyFile\UserId Stores a unique identifier generated for each infected user.
Registry Key HKLM\SOFTWARE\Microsoft\Cryptography\MachineGuid System identifier used for machine fingerprinting.
Process Target chrome.exe Google Chrome process terminated prior to browser profile manipulation.
Obfuscation Key R8Qx2mL7WkP9N4Yt-A5639182047 XOR key used for Base64 string obfuscation within the malware.
Technique Character Shift Obfuscation Strings such as “Google”, “Chrome”, and “chrome.exe” are stored with each character incremented by +1 and decoded at runtime.

Comments

Popular posts from this blog

Beware of Fake 7zip Installer: upStage Proxy

TamperedChef: Suspicious Recipe App is really Malware

EvilAI: Fake Online Speedtest Application