This started with an unexpected PrivacyKeeper download after a visit to coudflare[.]com. I wanted to understand what had landed on my computer, not assume that a suspicious-looking domain told the whole story.
Our static analysis found a signed MSIX package configured to load an application page from a remote server. The bundled runtime also contained a custom interface for desktop input and window control, with references to browser search settings. Those findings connect this specimen to previously reported browser-hijacking software.
We inspected the files without installing the package or fetching its remote application.
It does not authenticate the HTML or JavaScript a remote server supplies later.
The recorded download path.
The original file's download metadata named initpk.private-keeper[.]com. Its application configuration pointed to a different host, cdn.privacy-keeper[.]app. These are different roles: one identifies a recorded download origin; the other is a configured source of application logic.
From a typo to a local package
Reported visit and local download metadata.
The endpoint question was more useful: what did the downloaded software have the ability to do?
The application logic sits outside the signed container.
The package identifies as PrivacyKeeper.PrivacyKeeper, version 3.25.100.0. It uses NW.js, which combines a web interface with Node.js capabilities in a desktop application. Its configuration requests broad remote trust and a hidden starting window.
Read the configuration as a trust decision
Selected fields from the inspected package, normalized and defanged for display. This is not a complete or runnable manifest.
main: hxxps://cdn.privacy-keeper[.]app/
privacykeeper/src/browser.wv2.html
nodejs: true
node-remote: *://*
window.show: false
window.show_in_taskbar: false
chromium-args: --disable-web-securityThe package also declares runFullTrust. That permits desktop application behavior under the user's permissions; it does not confer administrator or SYSTEM access. The web-security flag is another concern, but it is not a certificate-error bypass.
What the signature does, and does not, cover
Signed container
- Launcher and bundled runtime
- Configuration pointing to remote HTML
- Custom native automation interface
Server-supplied logic
- Configured application entry page
- Content supplied at runtime
- Not covered by this local package signature
This is the useful lesson for software review: ask what a signed application delegates after launch. A package can remain unchanged while the server-supplied logic changes.
More than a risky setting.
The stronger finding was inside nw.dll. The analysis recovered an embedded API schema and registration name for nw.App.secSettings, alongside action-parsing strings, executable-code references, native input and window-control imports, and a browser-settings target.
The native interface, in evidence
Static markers from this specimen. This is a capability map, not a recovered command sequence.
Accept an action object
actions · cmd · cmdParams · appRegex
Schema, registration data, parameter checks, and code references support a custom action interface.
Generate desktop input
SendInput
Input-related messages and native call candidates support synthetic keyboard and mouse interaction.
Manipulate a window
MoveWindow · ShowWindow
Window-control markers sit alongside the input functionality.
Target browser settings
addressBar · addBtn · defaultBtn
A specific browser-settings destination gives the automation a concrete intended use.
Synthetic input could operate an already-running browser, which could then write a setting or retrieve an extension. A hunt limited to suspicious child processes could miss that behavior.
A Bing search URL appears beside the automation settings. Its presence does not establish a changed search provider or make Bing a malicious destination.
Published research connects this specimen to known browser-hijacking activity. Intezer's NinjaMare research describes the distinctive secSettings interface and lists the same PrivacyKeeper CDN, with a different entry-page filename. Trinity Cyber's PhantomJack research documents related NW.js browser hijacking and distribution through typo traffic. ThreatFox has an exact-hash entry with browser-hijacker tags; its formal family field remains unknown. The behavioral overlaps are more useful than forcing the labels to agree.
Investigate what happened, one state at a time.
Use separate evidence for receipt, installation, execution, and browser changes.
The evidence ladder
What to establish on a host, and where this investigation stands.
- 01ReceiptArtifact available
Exact file, download origin, and retained metadata.
- 02InstallationHistory unresolved
Package identity, publisher, deployment events, and user scope.
- 03Launch or DLL loadHistory unresolved
Process and image-load events tied to the inspected bytes.
- 04Network contactNot established
Initiating process, destination, timestamp, and connection outcome.
- 05Browser changesNot established
Search providers, extensions, policies, and profile timelines.
Preserve the records needed to answer each question.
- Preserve the download before cleanup.Record the hash, origin metadata, and encounter time. Retain relevant browser, endpoint, and proxy logs. Do not launch the file to test whether it is dangerous.
- Check installation and execution separately.Search package and deployment history, then launcher and DLL-load events. A file in quarantine or an analyst workspace is not proof of execution on a user's desktop.
- Correlate contact with a process.A visit to a host is weaker than contact from the launcher at the same time as a related browser change. Keep blocked attempts separate from successful connections.
- Compare the browser with its approved baseline.Look at extensions, search providers, homepage settings, and managed policies. Review whole policy-key deletion as well as individual value changes. Legitimate administration can produce those events too.
- Match response to the evidence.Confirmed launcher execution or a matching modified-DLL load warrants incident triage and consideration of containment. Preserve the relevant records before removal or browser repair.
Get-AppxPackage -Name '*PrivacyKeeper*' |
Select-Object Name, PackageFullName, Publisher, VersionThis checks the current user's registered packages. It does not establish past installation or cover every user. Use authorized inventory appropriate to your scope.
Hunt the hostname, not a substring
A download-origin hunt should parse the URL and compare its host. Otherwise, a domain appearing inside an unrelated URL's query string can become a false match.
// Draft query. Set the window to available retention.
let Origin = replace_string(
"initpk.private-keeper[.]com", "[.]", ".");
DeviceFileEvents
| where Timestamp > ago(30d)
| extend OriginHost = trim_end(@"\.$",
tolower(tostring(parse_url(FileOriginUrl).Host)))
| where OriginHost == Origin
| project Timestamp, DeviceId, ActionType,
FileName, SHA1, SHA256, OriginHostThe companion adds DNS, process, policy, and browser-profile pivots to this receipt query. Registry and file events locate changes to inspect; compare the actual settings with an approved baseline.
Download the draft hunt starters (.kql)Read the hunt coverage guide before using these read-only templates. They have not been run or performance-tested in a Defender tenant.
The next download alert needs a better question.
“Is it signed?” is worth asking. “What code will it trust after launch?” is the question that exposed the more consequential design here.
Our goal is to give defenders evidence they can act on. Build the investigation around what ran and what changed, with the original download preserved for comparison.
Primary sources and further reading
- Intezer: Rubber Ducky in the Sky, September 1, 2026.
- Trinity Cyber: Blurred Lines, November 5, 2025.
- ThreatFox: exact specimen hash entry 1910822.
- NW.js: Manifest format, security model, and App API reference.
- Microsoft: capability declarations, MSIX signing, and DeviceFileEvents schema.
