1. Web page (externally connected) sends a request to the extension. 2. Extension connects to a local native host via chrome.runtime.connectNative. 3. Extension forwards the request to the native host. 4. Native host processes the request and sends a response back. 5. Extension relays the response to the web page via the callback.

Target users: Developers integrating with NCB (National Computer Board) systems / Internal NCB employees using local security tools

The extension is a passive bridge; the actual 'login' or 'paid' logic resides in the destination services (ncbdt.local, etc.) or the native host application, which are not part of this extension package.

Monetization

No paid features detected

The extension is described as a 'Security Application Development Kit' and functions as a technical bridge. There is no evidence of subscription gates, payment UI, or license checks within the extension code. It is a utility tool for developers/integrators.

Confidence: 95
Payment platform: --
Source: AI / High
Login required: No
Reason: The extension is a background bridge for native messaging. It does not implement any login UI, credential storage, or authentication logic. It relies on the host application (native host) and the destination web pages (ncbdt.local, ncbmip.com, ncbchina.cn) to handle user sessions. The extension itself does not require the user to log in to the extension to function.

Permission risk

High-risk permissions

This estimate uses declared permissions and host permissions to assess access scope and sensitivity.

敏感权限：nativeMessaging

Publisher

ncbchina

Independent publisher

Email: [email protected]
Phone: --
Address: --

Public contact fields are shown above. Developer portfolio pages are available on paid accounts.

View developer portfolio

Permissions

Host access