registry / @hostinger/mcp / 3.28.1
@hostinger/mcp@3.28.1
MCP server for Hostinger API
AI Security Review
scanned 9h ago · by lpm-firewall-aiThe source shows a Hostinger MCP server whose OAuth flow uses auth.hostinger.com and whose API requests use developers.hostinger.com by default. The scanner's credential-redirection lead was not substantiated in the inspected skill source.
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
OAuth begins when the user signs in; API calls occur when MCP tools are used; the build command runs when the user invokes the build script.
Impact
The inspected source does not show credential redirection to an unrelated host, covert collection, or malicious automatic actions.
Mechanism
OAuth credentials go through Hostinger's authorization flow, and API bearer tokens are sent to the Hostinger API endpoint by default. The API endpoint can be changed with API_BASE_URL.
AI rationale
The source shows a Hostinger MCP server whose OAuth flow uses auth.hostinger.com and whose API requests use developers.hostinger.com by default. The scanner's credential-redirection lead was not substantiated in the inspected skill source.
Evidence
~/.config/hostinger-mcp/credentials.json%APPDATA%\hostinger-mcp\credentials.json./dist/package.json
Network endpoints2
auth.hostinger.comdevelopers.hostinger.com
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest points the package entry point and executable commands to Hostinger MCP server files.
- OAuth uses auth.hostinger.com and opens a browser for the authorization flow.
- Runtime API requests use a bearer token and default to developers.hostinger.com; API_BASE_URL can override that endpoint.
- The declared build script runs npx tsc and writes build output; no malicious behavior was identified in that flow.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
8 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/mcp@3.27.1
matchedPath = build.js
matchedIdentity = npm:QGhvc3Rpbmdlci9tY3A:3.27.1
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 unpkgsrc/core/skills.jsView file
Findings
1 Critical8 High3 Medium4 Low
CriticalPrevious Version Dangerous Deltasrc/core/skills.js
HighChild Processbuild.js
HighShell
HighCredential Redirect Persistencesrc/core/skills.js
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
Low
Affected versions and remediation
This report applies to @hostinger/mcp@3.28.1.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.28.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.