@hostinger/mcp@2.7.0
MCP server for Hostinger API
AI Security Review
scanned 1mo ago · by lpm-firewall-aiCached service credentials can be forwarded to an unrestricted operator-configured destination, warranting a credential exposure warning. The inspected behavior does not support a malicious publication block.
Static reason
One or more suspicious static signals were detected.
Trigger
Set API_BASE_URL to another destination and invoke an API operation through the MCP server with cached OAuth credentials available.
Impact
The configured recipient could receive a Hostinger access token and exercise its permissions.
Mechanism
The runtime resolves the cached access token, attaches bearer authentication, and sends the request without a destination allowlist.
AI rationale
Cached service credentials can be forwarded to an unrestricted operator-configured destination, warranting a credential exposure warning. The inspected behavior does not support a malicious publication block.
Evidence
src/servers/all.jssrc/core/runtime.jssrc/core/oauth.js
Network endpoints2
developers.hostinger.comauth.hostinger.com
Decision evidence
public snapshotAI called this Suspicious at 94.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- package.json has no automatic install lifecycle hook; build.js invokes the TypeScript compiler through an explicit build command.
- The active entrypoint starts the shared MCP runtime.
- The OAuth provider reuses an existing cached access token.
- The runtime accepts API_BASE_URL without restricting its destination.
- API calls attach the resolved token as bearer authentication and send it through axios.
- An MCP execute request activates API operations.
Evidence against
- Default API and OAuth destinations belong to Hostinger.
- No covert recipient or malicious installation behavior 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 · L1817// Run TypeScript compiler
console.log('Compiling TypeScript...');
exec('npx tsc', (error, stdout, stderr) => {
if (error) {
console.error('E
Medium
Suspicious Lifecycle Evidence
package.json has no automatic install lifecycle hook; build.js invokes the TypeScript compiler through an 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
MediumSuspicious Lifecycle Evidencebuild.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @hostinger/mcp@2.7.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@2.7.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.