@hostinger/mcp@2.3.0
MCP server for Hostinger API
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe active runtime forwards an existing token to a destination selected through an unrestricted environment variable. This warrants a warning under the credential-forwarding policy, while the inspected package contains no concrete malicious lifecycle behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs the MCP server with both a bearer token and a custom API base URL.
Impact
A service token could be sent to an unrestricted operator-configured endpoint.
Mechanism
The runtime resolves a token from the environment, builds request URLs from the configured base URL, and places that token in the Authorization header.
AI rationale
The active runtime forwards an existing token to a destination selected through an unrestricted environment variable. This warrants a warning under the credential-forwarding policy, while the inspected package contains no concrete malicious lifecycle behavior.
Evidence
src/core/runtime.jssrc/core/oauth.js
Network endpoints1
developers.hostinger.com
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The package exposes MCP server entrypoints and has no install lifecycle hook.
- The build script runs only through the explicit build command.
- An environment setting can replace the default API host without destination validation.
- The runtime obtains a bearer token and attaches it to requests built from that base URL.
- The bearer token can originate from Hostinger-related environment variables.
Evidence against
- No hidden install-time execution or automatic persistence was found.
- The default network destination is the Hostinger developer host.
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 · L1817// Run TypeScript compiler
console.log('Compiling TypeScript...');
exec('npx tsc', (error, stdout, stderr) => {
if (error) {
console.error
Medium
Ai Review Evidence
The build script runs only through the explicit build command.
build.jsView on unpkg · L17package.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
MediumAi Review Evidencebuild.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @hostinger/mcp@2.3.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@2.3.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.