Cybereinforce Threat Enforcement extension

Security at a glance

Some riskSafety score 80/10016 findings

Automated estimate from our latest scan (malware, permissions, obfuscation) — not a security audit. Higher safety score is better.

See the full security report

Chrome listing ID: cegphdldcnnemkjjblpekbmkocbepkbi

Permissions (5)

  • Block network requests (declarative)
  • Block requests with host access
  • Store local data

Frequently asked questions

Is Cybereinforce Threat Enforcement safe to use?

Our latest automated scan rates the Chrome listing of Cybereinforce Threat Enforcement at 80/100 (some risk) — malware, permission and obfuscation checks combined. The full report lists every finding behind the number. This is an automated estimate, not a guarantee of safety.

What permissions does Cybereinforce Threat Enforcement require?

Cybereinforce Threat Enforcement requests 5 permissions. The most significant: Block network requests (declarative), Block requests with host access, Store local data. See the full breakdown in the security report.

Who develops Cybereinforce Threat Enforcement?

Cybereinforce Threat Enforcement is published by Cybeurope Google. Impersonators copy popular extension names, so always verify the developer line and listing id on the store page before installing.

What this assessment covers

Store listing
Chrome
Checked version
1.3.1
Current listed version
1.3.1
Scan date (UTC)
Assessment status
Completed

Recorded findings: 1 critical and 2 high severity. Read the finding details before interpreting the score; automated flags are not proof of malicious behaviour.

Automated analysis looks for suspicious code, permissions and other risk signals. It does not observe every runtime behaviour or independently audit the publisher’s servers. A low-risk result is not a guarantee of safety. How our checks work.

Compare extensions by task