@hostinger/mcp@2.13.0
MCP server for Hostinger API
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe package's normal default is its Hostinger API, but its runtime forwards bearer credentials to an operator-configurable base URL without a destination allowlist in the inspected request path. This is a conditional credential exposure risk, so it warrants a warning rather than a block.
Static reason
One or more suspicious static signals were detected.
Trigger
An API tool call while API_BASE_URL is set to a custom destination.
Impact
A custom destination can receive the Hostinger bearer token, potentially exposing access associated with that credential.
Mechanism
The runtime builds the request URL from API_BASE_URL and adds the token returned by its environment-or-OAuth credential provider to the Authorization header; no destination allowlist is shown in the inspected path.
AI rationale
The package's normal default is its Hostinger API, but its runtime forwards bearer credentials to an operator-configurable base URL without a destination allowlist in the inspected request path. This is a conditional credential exposure risk, so it warrants a warning rather than a block.
Evidence
src/core/runtime.js
Network endpoints1
developers.hostinger.com
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The active server entrypoint starts the shared runtime for Hostinger tools.
- The runtime accepts API_BASE_URL with a Hostinger API default and obtains a bearer token from environment credentials or OAuth.
- Runtime API requests construct URLs from that base and attach the bearer token in the Authorization header, so a custom base can receive the credential.
- The package provides build.js as a build script; that file runs the TypeScript compiler and copies package files.
Evidence against
- The manifest identifies the package as a Hostinger API MCP server and has no install lifecycle hook.
- The flagged build command is invoked by the build script and only compiles TypeScript and copies build files.
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 · L18src/servers/all.jsView file
1#!/usr/bin/env node
// Auto-generated entry for group: all
import { startServer } from '../core/runtime.js';
import tools from '../core/tools/all.js';
import instructions
Medium
Ai Review Evidence
The active server entrypoint starts the shared runtime for Hostinger tools.
src/servers/all.jsView on unpkg · L1Findings
3 High5 Medium4 Low
HighChild Processbuild.js
HighShell
HighRuntime Package Installbuild.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumAi Review Evidencesrc/servers/all.js
MediumAi Review Evidencesrc/core/runtime.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @hostinger/mcp@2.13.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@2.13.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.