registry / @hostinger/mcp / 1.60.0
@hostinger/mcp@1.60.0
MCP server for Hostinger API
AI Security Review
scanned 18d ago · by lpm-firewall-aiInspected source shows ordinary Hostinger API and OAuth functionality, and the package manifest has no install lifecycle hook. The flagged build command compiles TypeScript; no concrete attack behavior was established.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The server runs when launched; API actions occur through tool requests, and OAuth sign-in is explicitly started.
Impact
No confirmed unauthorized data transfer, persistence, or destructive behavior was found.
Mechanism
The build script compiles TypeScript. The runtime sends bearer tokens to the configured API base URL, defaulting to Hostinger's developer API.
AI rationale
Inspected source shows ordinary Hostinger API and OAuth functionality, and the package manifest has no install lifecycle hook. The flagged build command compiles TypeScript; no concrete attack behavior was established.
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 defines start, build, and start:ts scripts, with no preinstall, install, or postinstall hook.
- The all-tools file lists user-invoked Hostinger API tools, including a deployment tool marked destructive.
- build.js runs the TypeScript compiler and copies package files into the build output.
- OAuth uses Hostinger's authentication service by default, and the runtime sends bearer tokens to its configured API base URL, which defaults to Hostinger's developer API.
- OAuth credentials are saved through the provider's credential file write path.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
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 · L18src/core/oauth.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @hostinger/mcp@1.59.0
matchedIdentity = npm:QGhvc3Rpbmdlci9tY3A:1.59.0
similarity = 0.946
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
Findings
1 Critical3 High3 Medium5 Low
CriticalPrevious Version Dangerous Deltasrc/core/oauth.js
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
Affected versions and remediation
This report applies to @hostinger/mcp@1.60.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@1.60.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.