registry / @hostinger/mcp / 3.6.1
@hostinger/mcp@3.6.1
MCP server for Hostinger API
AI Security Review
scanned 14d ago · by lpm-firewall-aiSource inspection found ordinary Hostinger MCP functionality, with interactive OAuth using Hostinger’s authentication service by default and caller-configured endpoints. The similarity hints correspond to package setup and utility sources; no concrete attack behavior was found.
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
Normal server or CLI use; package.json declares no install lifecycle hook.
Impact
No unauthorized credential transfer, persistence, destructive behavior, or unconsented account action was established.
Mechanism
OAuth uses a browser sign-in flow and sends tokens to the configured issuer; runtime API calls use the configured API base.
AI rationale
Source inspection found ordinary Hostinger MCP functionality, with interactive OAuth using Hostinger’s authentication service by default and caller-configured endpoints. The similarity hints correspond to package setup and utility sources; no concrete attack behavior was found.
Decision evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json declares only start, build, and start:ts scripts; the package entrypoint is the MCP server.
- OAuth defaults to Hostinger’s authentication service, starts a browser sign-in flow, and sends the authorization exchange to the selected issuer. The issuer override is caller-configured.
- The runtime defaults API calls to Hostinger’s developer API and attaches the bearer token to those requests; the API base can be explicitly configured by the caller.
- Bundled skills are served as MCP skill resources, and the runtime exposes them through skill handlers.
- The flagged bootstrap, build, and logo utility sources show server sign-in setup, TypeScript compilation, and local font-file processing.
- Inspected dependency sources identify standard MCP transport, HTTP client, and CORS middleware behavior. The cited excerpts show no attack behavior.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
Source & flagged code
10 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 Critical10 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
HighKnown Malware Source Similaritysrc/core/skills.js
HighKnown Malware Source Similaritysrc/core/skills.ts
HighKnown Malware Source Similarityskills/headless/steps/05-design/logo-kit.mjs
MediumNetwork
Affected versions and remediation
This report applies to @hostinger/mcp@3.6.1.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.6.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.