@hostinger/mcp@2.5.0
MCP server for Hostinger API
AI Security Review
scanned 1mo ago · by lpm-firewall-aiStored service credentials can be forwarded to an unrestricted operator-configured destination, warranting a warning under the credential-forwarding policy. No concrete behavior supporting a malicious publication block was established.
Static reason
One or more suspicious static signals were detected.
Trigger
Override API_BASE_URL, run the MCP server with cached OAuth credentials, and invoke an API operation.
Impact
A destination outside Hostinger could receive a reusable Hostinger access token.
Mechanism
The runtime builds requests against the configured destination and attaches the independently resolved Hostinger bearer token without a destination allowlist.
AI rationale
Stored service credentials can be forwarded to an unrestricted operator-configured destination, warranting a warning under the credential-forwarding policy. No concrete behavior supporting a malicious publication block was established.
Evidence
src/core/runtime.jssrc/core/oauth.jscredentials.json
Network endpoints2
developers.hostinger.comauth.hostinger.com
Decision evidence
public snapshotAI called this Suspicious at 95.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- package.json has no automatic install lifecycle hook; build.js explicitly invokes the TypeScript compiler.
- The runtime accepts API_BASE_URL without restricting the destination to Hostinger.
- The OAuth provider reads stored credentials and reuses an unexpired access token.
- API requests attach the resolved token as bearer authentication and send it through Axios.
- MCP operation execution activates the authenticated API request path.
Evidence against
- The default API and OAuth destinations belong to Hostinger.
- Credential exposure requires an overridden destination and an API operation; no covert recipient or malicious intent was established.
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 · L1818console.log('Compiling TypeScript...');
exec('npx tsc', (error, stdout, stderr) => {
if (error) {
console.error('Error compiling TypeScript:', error);
consol
Medium
Suspicious Lifecycle Evidence
package.json has no automatic install lifecycle hook; build.js explicitly invokes the TypeScript compiler.
build.jsView on unpkg · L18package.jsonView file
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
MediumSuspicious Lifecycle Evidencebuild.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @hostinger/mcp@2.5.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@2.5.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.