registry / @hostinger/mcp / 2.18.0
@hostinger/mcp@2.18.0
MCP server for Hostinger API
AI Security Review
scanned 21d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and its build command is explicit build-time compilation. The inspected runtime credential transfers follow the Hostinger API and upload flow, with no concrete attack behavior established.
Static reason
One or more suspicious static signals were detected.
Trigger
A user starts the MCP server or invokes an upload operation.
Impact
These requests enable API operations and requested file uploads; no unrelated credential recipient or unconsented install-time action was identified.
Mechanism
The runtime sends bearer credentials to API URLs under its configured API base, then uses upload credentials returned by that API at its provided upload URL.
AI rationale
The package has no install lifecycle hook, and its build command is explicit build-time compilation. The inspected runtime credential transfers follow the Hostinger API and upload flow, with no concrete attack behavior established.
Evidence
package.jsonbuild.jssrc/core/runtime.js
Network endpoints1
developers.hostinger.com
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines start and build scripts but no preinstall, install, or postinstall hook.
- build.js runs the TypeScript compiler as part of the build script.
- Runtime API calls default to developers.hostinger.com; an operator can configure API_BASE_URL.
- The flagged runtime requests attach a bearer token to URLs built under the configured API base.
- Upload credentials are obtained from the authenticated API response and used with the returned upload URL for file transfers.
Evidence against
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 · L1813if (!fs.existsSync('./dist')) {
fs.mkdirSync('./dist');
}
// Run TypeScript compiler
console.log('Compiling TypeScript...');
exec('npx tsc', (error, stdout, stderr) => {
if (error) {
console.error('Error compiling TypeScript:', error);
console.error(stderr);
process.exit(1);
}
if (stdout) {
console.log(stdout);
}
consol
Low
Ai Review Evidence
build.js runs the TypeScript compiler as part of the build script.
build.jsView on unpkg · L13Findings
3 High3 Medium6 Low
HighChild Processbuild.js
HighShell
HighRuntime Package Installbuild.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencebuild.js
Affected versions and remediation
This report applies to @hostinger/mcp@2.18.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@2.18.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.