registry / @hostinger/mcp / 3.11.0
@hostinger/mcp@3.11.0
MCP server for Hostinger API
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged process execution belongs to an explicit TypeScript build or a user-invoked Hostinger sign-in flow. OAuth traffic goes to Hostinger’s issuer, and the reviewed sources show no unrelated credential collection or exfiltration.
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 MCP server starts when its entry point is run; browser sign-in occurs when the headless bootstrap is invoked and no usable credentials are found.
Impact
Expected Hostinger API operations and local OAuth credential storage; no unrelated credential collection or attack behavior was found.
Mechanism
The server connects to Hostinger services for API and OAuth operations. OAuth tokens are saved in the user’s Hostinger MCP configuration directory.
AI rationale
The flagged process execution belongs to an explicit TypeScript build or a user-invoked Hostinger sign-in flow. OAuth traffic goes to Hostinger’s issuer, and the reviewed sources show no unrelated credential collection or exfiltration.
Evidence
~/.config/hostinger-mcp/credentials.json%APPDATA%/hostinger-mcp/credentials.jsondist/
Network endpoints1
auth.hostinger.com
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package entry points to its Hostinger MCP server; the manifest declares no install lifecycle scripts.
- The build script runs `npx tsc` when explicitly invoked and copies build artifacts.
- OAuth uses Hostinger’s auth issuer and exchanges authorization or refresh tokens with that issuer.
- OAuth credentials are stored in the user’s Hostinger MCP configuration directory.
- The headless bootstrap starts login only when existing credentials are absent and uses a browser sign-in flow.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedUrlStrings
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.11.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.11.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.