registry / @hostinger/mcp / 3.9.0
@hostinger/mcp@3.9.0
MCP server for Hostinger API
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe flagged process execution is part of an explicit build script, while the OAuth flow sends tokens to Hostinger’s auth service and API requests use the Hostinger API base URL. The reviewed login flow is user-invoked, and no malicious behavior was identified.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
The server starts when its entrypoint is invoked; OAuth sign-in is explicitly selected with `--login`, and API calls follow tool requests.
Impact
No unauthorized credential transfer, install-time contact, or concealed automatic action was identified.
Mechanism
OAuth tokens are used with Hostinger’s auth and API endpoints. The build script runs the TypeScript compiler when the build script is invoked.
AI rationale
The flagged process execution is part of an explicit build script, while the OAuth flow sends tokens to Hostinger’s auth service and API requests use the Hostinger API base URL. The reviewed login flow is user-invoked, and no malicious behavior was identified.
Evidence
~/.config/hostinger-mcp/credentials.json%APPDATA%/hostinger-mcp/credentials.json./dist
Network endpoints2
auth.hostinger.comdevelopers.hostinger.com
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package identifies itself as Hostinger’s MCP server.
- The `npx tsc` child process runs in the explicit build script, not an install lifecycle hook.
- OAuth uses Hostinger’s auth service, and refresh tokens are sent to its token endpoint.
- The browser sign-in flow starts only with the explicit `--login` option.
- API calls use the configured Hostinger API base URL and obtain a token for those requests.
Evidence against
- OAuth credentials are stored under the user’s `hostinger-mcp` configuration directory.
- The package exposes account and billing operations that can have significant effects when explicitly invoked.
- The flagged bootstrap invokes the package through `npx` and forwards its interactive login flow.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
9 flaggedbuild.jsView file
2L3: import { exec } from 'child_process';
L4: import fs from 'fs';
High
18console.log('Compiling TypeScript...');
L19: exec('npx tsc', (error, stdout, stderr) => {
L20: if (error) {
High
Runtime Package Install
Package source invokes a package manager install command at runtime.
build.jsView on unpkg · L18•matchType = normalized_sha256
matchedPackage = hostinger-api-mcp@3.5.0
matchedPath = build.js
matchedIdentity = npm:aG9zdGluZ2VyLWFwaS1tY3A:3.5.0
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
build.jsView on unpkgskills/headless/connect/bootstrap.mjs
Findings
10 High3 Medium4 Low
HighChild Processbuild.js
HighShell
HighRuntime Package Installbuild.js
HighKnown Malware Source Similarityskills/headless/connect/bootstrap.mjs
HighKnown Malware Source Similaritysrc/core/oauth.js
HighKnown Malware Source Similaritysrc/core/oauth.ts
HighKnown Malware Source Similaritybuild.js
HighKnown Malware Source Similaritysrc/core/skills.js
HighKnown Malware Source Similaritysrc/core/skills.ts
HighKnown Malware Source Similarityskills/headless/steps/05-design/logo-kit.mjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
Affected versions and remediation
This report applies to @hostinger/mcp@3.9.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.9.0 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.