@hostinger/mcp@3.7.1
MCP server for Hostinger API
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe source permits environment-configured destinations to receive saved Hostinger credentials without an allowlist. Since the defaults are Hostinger endpoints and an alternate destination requires operator configuration, this is a conditional credential exposure warning, not proof of malicious behavior.
Decision evidence
public snapshot- The package manifest has no install lifecycle hook; its scripts are start, build, and start:ts.
- The OAuth provider loads saved credentials and accepts OAUTH_ISSUER as an override to its Hostinger default.
- When refreshing a saved session, the provider sends its refresh token to the configured issuer without a destination allowlist.
- Runtime API calls use API_BASE_URL to build the request URL and attach the bearer token to the request.
- The main server entrypoint starts the runtime with the package’s tools and skills.
- The default OAuth issuer and API host are Hostinger endpoints.
- The alternate destinations require operator-supplied environment configuration; the inspected source does not show an automatic third-party destination.
Source & flagged code
9 flaggedPackage source invokes a package manager install command at runtime.
build.jsView on unpkg · L18Source file is highly similar to a previously finalized malicious package; route for source-aware review.
build.jsView on unpkgFindings
Affected versions and remediation
This report applies to @hostinger/mcp@3.7.1.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.7.1 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.