Is Q-bot 2.0 safe?

Medium risk

Q-bot 2.0 is medium risk. Q-bot 2.0's popup proxy toggle embeds a fixed username and password for the proxy at 85.237.204.177:8385. The extension lacks Chrome's proxy permission, so the toggle may not work at runtime, but the credentials still ship in the package.

optionup89v3.8.5Chrome Web Store
45Risk
Who publishes it

optionup89 - 1 other listing from the same operator, 1 of them carrying a finding

What this publisher told the store about itself, and the other listings that told it the same thing.

Publisher
optionup89

Same store account

1 other listing published from this account, 1k+ users between them. 1 of them carries a finding.

AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.

Publishers can request a review.

Findings

Popup ships fixed proxy credentials for 85.237.204.177:8385.

Q-bot 2.0's popup proxy toggle embeds a fixed username and password for the proxy at 85.237.204.177:8385.

The extension lacks Chrome's proxy permission, so the toggle may not work at runtime, but the credentials still ship in the package.

Severity
Medium unwanted
Type
Unexpected
CWE
CWE-522
Source
Dynamic sandbox
What actually happens
You did this

The user enables the proxy toggle in the extension popup.

The extension did this

The extension attempts to configure a fixed HTTP proxy and includes the proxy credentials in its packaged source.

Captured request
POST85.237.204.177:8385
Fields included in the proxy configuration
  • Proxy credentials
    username plus redacted password

    A fixed username and password can grant access to the configured proxy service if the credentials remain valid.

Observation

Observed during dynamic analysis: the extension package includes fixed proxy credentials, but the manifest does not request Chrome's proxy permission, so the popup toggle may not successfully apply the proxy setting at runtime.

Updated 30 September 2026hlfihkgnacdflbmmcpdlhibegfnhggjb