registry / @hostinger/mcp / 3.8.0
@hostinger/mcp@3.8.0
MCP server for Hostinger API
AI Security Review
scanned 13d ago · by lpm-firewall-aiSource inspection found no lifecycle hook or concrete malicious behavior. The similarity flags are not proof: the reviewed OAuth, runtime, and generated skill paths align with the Hostinger API server’s declared function.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
A user runs a declared server command or invokes the headless connection flow.
Impact
The reviewed behavior supports the package’s stated API integration, with no confirmed credential disclosure to an unrelated recipient or unrequested account action.
Mechanism
The server obtains credentials for the configured OAuth issuer and sends API requests to the configured API base URL; the defaults point to Hostinger services.
AI rationale
Source inspection found no lifecycle hook or concrete malicious behavior. The similarity flags are not proof: the reviewed OAuth, runtime, and generated skill paths align with the Hostinger API server’s declared function.
Evidence
package.jsonsrc/core/oauth.jssrc/core/oauth.tssrc/core/runtime.jsskills/headless/connect/bootstrap.mjs
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
- package.json has no install lifecycle hook and exposes the server through its declared entrypoints.
- OAuth credentials are sent to the configured issuer, which defaults to Hostinger’s authentication service; token exchange and refresh use that issuer.
- The bootstrap invokes the Hostinger MCP login flow, and the server sends API requests to its configured Hostinger API base URL.
- The flagged skill and tool files contain generated MCP skill and tool data; the reviewed excerpts show no install-time execution or credential export.
- Inspected SDK, Axios, and CORS excerpts show package metadata, transport setup, cancellation handling, and middleware defaults.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
9 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
10 High3 Medium4 Low
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
HighKnown Malware Source Similaritysrc/core/skills.js
HighKnown Malware Source Similaritysrc/core/skills.ts
HighKnown Malware Source Similarityskills/headless/steps/05-design/logo-kit.mjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
Affected versions and remediation
This report applies to @hostinger/mcp@3.8.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.8.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.