registry / @hostinger/mcp / 3.12.2
@hostinger/mcp@3.12.2
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged process execution is limited to TypeScript compilation and the optional bootstrap’s package launch. OAuth credentials are exchanged with the configured Hostinger issuer and saved in the package’s user-specific credentials file; no install-time collection or unrelated account action 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
The server runs when launched; OAuth sign-in runs only when requested with `--login` or when authentication is needed and no usable credentials are available.
Impact
No unauthorized data transfer, account action, or install-time behavior was identified in the inspected paths.
Mechanism
The package authenticates to Hostinger’s API using a configured token or OAuth credentials. The OAuth default issuer is auth.hostinger.com; the bootstrap’s npx invocation occurs only when that bootstrap is run.
AI rationale
The flagged process execution is limited to TypeScript compilation and the optional bootstrap’s package launch. OAuth credentials are exchanged with the configured Hostinger issuer and saved in the package’s user-specific credentials file; no install-time collection or unrelated account action was found.
Evidence
~/.config/hostinger-mcp/credentials.json%APPDATA%/hostinger-mcp/credentials.json
Network endpoints1
auth.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 manifest has start/build scripts but no install lifecycle hook; its main and binaries point to Hostinger MCP server entry points.
- The build script runs `npx tsc` and copies project files into `dist`; it does not download or execute a remote payload.
- OAuth uses Hostinger’s auth issuer by default, and the issuer can be changed through an explicit environment setting.
- The OAuth flow exchanges authorization or refresh tokens with the configured issuer and stores credentials under the user’s Hostinger MCP config directory.
- The server exposes login as an explicit `--login` command; the headless bootstrap uses a browser sign-in flow when no saved credentials are found.
Evidence against
- The package reads API tokens and OAuth credentials, but the inspected flows use them for Hostinger API authentication and the Hostinger OAuth service.
- The headless bootstrap invokes `npx` to resolve this package when the bootstrap is run; no package install hook triggers that behavior.
Behavioral surface
ChildProcessCrypto
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.12.2.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.12.2 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.