registry / @hostinger/mcp / 3.17.0
@hostinger/mcp@3.17.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged process execution in `build.js` is a TypeScript build, while OAuth exchanges credentials with Hostinger and stores them locally. The headless bootstrap invokes the package CLI for a browser sign-in flow; I found no install-time collection, unrelated credential transfer, or hidden account action.
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 when a user runs its CLI or imports its main entry; OAuth runs when an API call needs authentication, and the headless bootstrap runs when the user follows that setup flow.
Impact
Expected Hostinger account operations use the user’s configured or authorized credentials; no unrelated collection or hidden action was found.
Mechanism
It sends API requests to Hostinger’s API and performs OAuth with Hostinger’s auth service; OAuth credentials are stored locally.
AI rationale
The flagged process execution in `build.js` is a TypeScript build, while OAuth exchanges credentials with Hostinger and stores them locally. The headless bootstrap invokes the package CLI for a browser sign-in flow; I found no install-time collection, unrelated credential transfer, or hidden account action.
Evidence
~/.config/hostinger-mcp/credentials.json%APPDATA%/hostinger-mcp/credentials.json
Network endpoints2
auth.hostinger.comdevelopers.hostinger.com
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package’s main and CLI entry point starts the Hostinger MCP server.
- OAuth uses Hostinger’s auth issuer for authorization and token exchange.
- The OAuth flow stores its credentials in a local Hostinger MCP config path.
- The headless bootstrap runs the package CLI and presents sign-in through a browser flow.
- The build script invokes the TypeScript compiler and copies project files.
Evidence against
- No install lifecycle scripts are declared.
- No credential transfer to an unrelated host or unrequested account action was identified.
- The new skill/bootstrap behavior is available through the package’s documented headless setup flow, not an install hook.
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.17.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.17.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.