@hostinger/mcp@1.63.2
MCP server for Hostinger API
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe active runtime can forward an existing Hostinger credential to an unrestricted operator-configured destination. The package has no automatic install hook or other concrete malware behavior in the inspected sources.
Static reason
One or more suspicious static signals were detected.
Trigger
Starting the MCP server and invoking an API tool while API_BASE_URL points to a non-Hostinger endpoint.
Impact
An operator-controlled endpoint could receive the Hostinger credential.
Mechanism
The runtime obtains a token, derives request URLs from API_BASE_URL, and places that token in the Authorization header.
AI rationale
The active runtime can forward an existing Hostinger credential to an unrestricted operator-configured destination. The package has no automatic install hook or other concrete malware behavior in the inspected sources.
Evidence
src/core/oauth.jssrc/core/runtime.js
Network endpoints1
developers.hostinger.com
Decision evidence
public snapshotAI called this Suspicious at 93.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The package exposes MCP server entry points and has no automatic install lifecycle script.
- The build helper only runs through the explicit build script and writes distribution metadata.
- The runtime accepts an unrestricted API base URL from an environment variable.
- A Hostinger API token can be read from environment variables.
- Requests constructed from that base URL attach the bearer token and send them with Axios.
Evidence against
- The default API endpoint is Hostinger's developer domain.
- No hidden install-time execution, self-dependency, or payload-loading behavior was found in the inspected entry, build, OAuth, and runtime code.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
4 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 · L1844// Create package.json in dist that points at compiled src/
const packageJson = JSON.parse(fs.readFileSync('./package.json', 'utf8'));
packageJson.main = 'src/servers/all.js';
if (packageJson.bin) {
for (const key of Object.keys(package
Medium
Ai Review Evidence
The build helper only runs through the explicit build script and writes distribution metadata.
build.jsView on unpkg · L44package.json
Findings
3 High5 Medium4 Low
HighChild Processbuild.js
HighShell
HighRuntime Package Installbuild.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumSuspicious Lifecycle Evidencepackage.json
MediumAi Review Evidencebuild.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @hostinger/mcp@1.63.2.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@1.63.2 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.