registry / @hostinger/mcp / 3.22.0
@hostinger/mcp@3.22.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged shell execution is limited to an explicitly run TypeScript build, while OAuth follows a Hostinger sign-in flow and stores its credentials locally. The headless bootstrap can run npx to obtain the MCP package when invoked, but the reviewed source does not show it exfiltrating credentials or performing unrelated actions.
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 runs when the server needs a token, or when a user explicitly requests --login; the build and headless bootstrap run when invoked.
Impact
No unrelated credential transmission or harmful automatic action was found.
Mechanism
The OAuth provider uses Hostinger's auth issuer and stores credentials locally. The MCP sends API requests to developers.hostinger.com by default.
AI rationale
The flagged shell execution is limited to an explicitly run TypeScript build, while OAuth follows a Hostinger sign-in flow and stores its credentials locally. The headless bootstrap can run npx to obtain the MCP package when invoked, but the reviewed source does not show it exfiltrating credentials or performing unrelated actions.
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 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exposes MCP server entry points and has no install lifecycle script in its manifest.
- OAuth uses Hostinger's auth service and exchanges tokens with that issuer.
- OAuth login is invoked by an explicit --login option; otherwise the provider uses an environment token or stored credentials before falling back to browser login.
- The build script runs npx tsc as part of an explicitly invoked build command.
Evidence against
- The headless bootstrap runs npx with @hostinger/mcp@latest when that bootstrap flow is invoked, so it can install a runtime package version.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
4 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 · L18skills/headless/connect/bootstrap.mjsView file
•matchType = normalized_sha256
matchedPackage = hostinger-api-mcp@3.5.0
matchedPath = [redacted].mjs
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.
Findings
1 Critical4 High3 Medium4 Low
CriticalPrevious Version Dangerous Deltasrc/core/oauth.ts
HighChild Processbuild.js
HighShell
HighRuntime Package Installbuild.js
HighKnown Malware Source Similarityskills/headless/connect/bootstrap.mjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @hostinger/mcp@3.22.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.22.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.