registry / @hostinger/mcp / 3.11.1
@hostinger/mcp@3.11.1
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged process execution is limited to an explicitly run build and a connection helper for this package. OAuth uses Hostinger's auth service and a browser callback, and credentials are stored in the expected user config location.
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 authentication is needed for an API call or when the user explicitly runs the login helper.
Impact
No unauthorized collection, account action, or concealed code execution was found.
Mechanism
The package exchanges OAuth credentials with Hostinger and stores them in the user's config directory; its optional build command compiles TypeScript.
AI rationale
The flagged process execution is limited to an explicitly run build and a connection helper for this package. OAuth uses Hostinger's auth service and a browser callback, and credentials are stored in the expected user config location.
Evidence
~/.config/hostinger-mcp/credentials.json./dist/
Network endpoints4
auth.hostinger.comdevelopers.hostinger.comraw.githubusercontent.comcodeload.github.com
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes server entry points and has no install lifecycle script.
- The build script runs the TypeScript compiler and writes build artifacts when explicitly run.
- The headless helper invokes npx to run this package when the helper is explicitly run.
- OAuth uses auth.hostinger.com by default and exchanges credentials through its authorization flow.
- OAuth credentials are saved to the user's hostinger-mcp config directory.
Evidence against
- Server startup does not itself invoke the headless bootstrap or OAuth login.
- The OAuth login opens a browser and waits for a localhost callback.
- The package's API base URL defaults to developers.hostinger.com and can be configured by the user.
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.1.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.11.1 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.