browserscan.net detects Incognito mode, WebGL exceptions and Incorrect RAM information in Wayfern

[DedInc]

What happened?

When testing on https://www.browserscan.net/, DonutBrowser (Wayfern Chromium engine) triggers three clear detections that significantly weaken its anti-fingerprinting / anti-detect capabilities:

1. Incognito mode

   You have Incognito mode turned on, which could be interpreted as an attempt to impersonate a completely new identity, especially in use cases where using promotional coupons, redeeming bonuses or voting should be limited to once per user.

2. WebGL exceptions

   The scanner explicitly reports WebGL exceptions.

3. Incorrect RAM information

   Your RAM information is incorrect. You appear to be hiding the actual hardware information.

Steps to reproduce

1. Launch the latest version of DonutBrowser.
2. Create a new clean profile using the Wayfern (Chromium) engine.
3. Open https://www.browserscan.net/
4. Scroll to the Incognito, WebGL and Hardware / RAM sections.

Expected Behavior

As an anti-detect browser, Wayfern should:

• Completely hide or properly spoof Incognito mode (make it indistinguishable from a normal window);
• Prevent any WebGL exceptions;
• Spoof realistic RAM information so the scanner cannot detect hardware masking.

Currently all three key anti-detect mechanisms are being bypassed by one popular fingerprinting scanner. This is critical for users relying on DonutBrowser to bypass advanced fingerprinting and anti-fraud systems.

Operating System

Windows

Donut Browser version

v0.19.0 (2026-04-04)

Which browser is affected?

Wayfern

Error logs or screenshots

[github-actions]

Thanks for opening your first issue!

Thank you for the detailed report with screenshots on the browserscan.net detections for Wayfern.

Missing information:

• Could you share the app logs from your session? On Windows, you can find them at %APPDATA%\DonutBrowser\logs\ — please attach the most recent log file. The logs will show what fingerprint values were generated and applied via CDP (especially the RAM/deviceMemory and WebGL-related fields).
• Did you modify any fingerprint settings in the profile configuration, or is this a completely default/fresh profile with no manual changes?
• Does the "WebGL exceptions" detection show any specific error message or details on browserscan.net? A full screenshot of the WebGL section (expanded) would be helpful.
• Is the "Block WebGL" option enabled in your profile's Wayfern config? (This could explain the WebGL detection.)
• For the RAM detection — does browserscan.net show what value it detected vs. what it expected?