MalDet · Static Security Report
This repository has a medium vulnerability score of 45, which means there are several insecure coding patterns that an attacker could exploit to steal secrets or code. However, the scan also found signs of potentially malicious intent with a low score of 3, suggesting the code might be intentionally harmful rather than just poorly written. Most of these issues relate to common mistakes like using unescaped user input in logs or allowing variable interpolation in scripts, which are typical errors that can be fixed by developers. There is only one high-severity finding involving an encoded payload being decoded and executed, but this appears to be a specific edge case rather than widespread malicious behavior. Overall, while the code contains some risky patterns that need attention, it does not look like a repository designed to cause harm, so you can proceed with caution if you are comfortable addressing the identified issues.
Written by a language model running locally on the scanning machine, from the findings in this report. The risk levels above and below were decided by the scoring model, not by this summary.
MalDet scores two different questions separately, because they call for different responses: code can be badly written without being hostile, and hostile code is not always badly written.
| Detector | Looks for | High | Medium | Low | Total |
|---|---|---|---|---|---|
| semgrep | Insecure coding patterns across many languages | 2 | 20 | 2 | 24 |
| yara | Signatures of malicious behaviour in source files | 3 | 0 | 1 | 4 |
| guarddog | Malicious package and install-time behaviour | 0 | 1 | 0 | 1 |
21 of 29 findings were rated more likely genuine than noise by the classifier.
Identical findings are grouped, so a single rule firing many times takes one row. Ordered worst first. “Seen” is how many times that finding occurred.
| Severity | Detector | Finding | Seen | Example location |
|---|---|---|---|---|
| high | semgrep | Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use | 2 | /.github/workflows/publish-tool-server.yml:80 |
| high | yara | YARA rule matched: detect_base64_exec — Encoded payload decoded and then executed | 1 | /mcp-tool-server/src/pages.js |
| high | yara | YARA rule matched: detect_obfuscated_string_execution — Reconstructs a string character-by-character or from hex escapes, then immediately executes it - fromCharCode/chr() alone are common in ordinary text-processing code, so this requires both the reconstruction and an execution call together | 2 | /mcp-app-server/src/shared.js |
| medium | semgrep | User data flows into the host portion of this manually-constructed HTML. This can introduce a Cross-Site-Scripting (XSS) vulnerability if this comes from user-provided input. Consider using a sanitization library such as DOMPurify to sanitize the HTML within. | 1 | /mcp-tool-server/src/libavoid-pass.js:289 |
| medium | guarddog | Detects LOLBAS usage in install hooks (execution and network tools) [threat-process-hooks] | 1 | /mcp-tool-server/package.json:15 |
| medium | semgrep | RegExp() called with a `name` function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use hardcoded regexes instead. If your regex is run on user-controlled | 1 | /shared/mx-xml.js:391 |
| medium | semgrep | GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: ac | 14 | /.github/workflows/publish-tool-server.yml:38 |
| medium | semgrep | Detected possible user input going into a `path.join` or `path.resolve` function. This could possibly lead to a path traversal vulnerability, where the attacker can access arbitrary files stored in the file system. Instead, be sure to sanitize or validate user input first. | 4 | /mcp-tool-server/src/cdn-cache.js:128 |
| low | semgrep | Detected a logger that logs user input without properly neutralizing the output. The log message could contain characters like ` ` and ` ` and cause an attacker to forge log entries or include malicious content into the logs. Use proper input validation and/or output encoding to prevent log entries | 2 | /mcp-app-server/src/index.js:227 |
| low | yara | YARA rule matched: detect_downloader — Downloads a remote resource - common and low-signal alone; see detect_download_and_execute for the composite version | 1 | /mcp-tool-server/vendor/libavoid/libavoid-node.mjs |