@hostinger/mcp@3.17.4
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package’s execution paths support building and running a Hostinger API MCP server, and its OAuth flow uses the Hostinger issuer by default. The flagged shell and network behavior is tied to compilation, browser sign-in, or user-requested API operations; no malicious automatic behavior was found.
Decision evidence
public snapshot- The package entry points start the Hostinger MCP server.
- The build script runs the TypeScript compiler and copies package files into dist.
- The headless connection bootstrap invokes the Hostinger MCP package through npx when that script is run.
- OAuth uses auth.hostinger.com by default and sends refresh tokens to the configured issuer’s token endpoint.
- OAuth credentials are saved to the Hostinger MCP config directory; on non-Windows platforms the file is restricted to owner access.
- Bundled agent skills are exposed as MCP resources through skills and resource requests.
- The package includes child-process and shell execution in its build and OAuth browser-launch code.
- The connection bootstrap checks for existing Hostinger credentials and can initiate a browser sign-in.
- The package handles API tokens and OAuth credentials to authenticate requests to Hostinger services.
- Bundled skills describe account operations and deployment workflows.
Source & flagged code
7 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.17.4.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.17.4 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.