registry / @hostinger/mcp / 3.14.1
@hostinger/mcp@3.14.1
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged child-process use supports TypeScript compilation and an explicit sign-in helper. OAuth targets Hostinger’s issuer, stores credentials locally, and is not initiated by the CLI’s default startup path.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
The server starts through its CLI entry point; OAuth sign-in requires `--login`, and token refresh is used for Hostinger API authentication.
Impact
No unauthorized data collection, unrelated credential transfer, or unsolicited account action was identified.
Mechanism
The build invokes the TypeScript compiler. OAuth exchanges and refreshes tokens with the Hostinger issuer and stores credentials locally.
AI rationale
The flagged child-process use supports TypeScript compilation and an explicit sign-in helper. OAuth targets Hostinger’s issuer, stores credentials locally, and is not initiated by the CLI’s default startup path.
Evidence
~/.config/hostinger-mcp/credentials.json%APPDATA%\hostinger-mcp\credentials.json
Network endpoints1
auth.hostinger.com
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package describes itself as a Hostinger API MCP server and exposes its server entry point through the main field and CLI binaries.
- The build script runs `npx tsc` to compile TypeScript; it does not install or execute downloaded application code.
- The OAuth sign-in flow runs only when `--login` is explicitly supplied.
- OAuth uses the Hostinger issuer and stores credentials in a local configuration file.
- The documented bootstrap helper resolves `@hostinger/mcp@latest` through npx to launch the package itself.
Evidence against
- The OAuth code reads and refreshes stored credentials, but sends them to the configured Hostinger issuer as part of its authentication flow.
- The bootstrap helper uses child-process execution, but its command arguments are fixed and it is a separate, documented setup helper.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
Source & flagged code
7 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 · L18•matchType = normalized_sha256
matchedPackage = hostinger-api-mcp@3.5.0
matchedPath = build.js
matchedIdentity = npm:aG9zdGluZ2VyLWFwaS1tY3A:3.5.0
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
build.jsView on unpkgskills/headless/connect/bootstrap.mjs
Findings
1 Critical7 High3 Medium4 Low
CriticalPrevious Version Dangerous Deltasrc/core/skills.js
HighChild Processbuild.js
HighShell
HighRuntime Package Installbuild.js
HighKnown Malware Source Similarityskills/headless/connect/bootstrap.mjs
HighKnown Malware Source Similaritysrc/core/oauth.js
HighKnown Malware Source Similaritysrc/core/oauth.ts
HighKnown Malware Source Similaritybuild.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to @hostinger/mcp@3.14.1.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.14.1 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.