Scan report

Psiphon-Labs / psiphon-tunnel-core

Vulnerability High

Could an attacker exploit mistakes in this code?

258 risk score

Serious issues. Review the high-severity findings before using it.

High
15
Medium
87
Low
0

Sources: Bandit, Semgrep, pip-audit

Malicious pattern Medium

Does this code look like it is trying to cause harm?

19 risk score

Real issues worth reviewing before you rely on this code.

High
7
Medium
5
Low
18

Sources: YARA, ClamAV, GuardDog, dependency checker

Findings overview
132 total findings
Likely real
76
Uncertain
34
Likely noise
22

The risk classifier rates every finding for how likely it is to be a real issue. Likely noise still counts, just much less.

What we found, in plain English

The repository has two distinct security issues that need immediate attention before it can be used in production. The most critical problem is that the code contains hardcoded private keys, which are extremely dangerous because anyone with access to this file can steal sensitive credentials and compromise the entire system. Additionally, there are several high-risk vulnerabilities related to unsafe coding practices, such as missing mutex locks that could cause crashes and untrusted input that might lead to cross-site scripting attacks. While some of these issues appear to be intentional obfuscation or malware evasion techniques rather than simple mistakes, they still represent significant security risks that should not be ignored. The developer should remove the hardcoded keys immediately and fix the unsafe patterns before deploying this code anywhere.

Written by a local language model from the findings below. The risk scores come from the classifier, not from this summary.

Detections by engine

  • Semgrep 102

    Pattern-based code analysis · Vulnerability

  • YARA 22

    Malware signature rules · Malicious pattern

  • GuardDog 8

    Supply-chain attack heuristics · Malicious pattern

Score over time

Overall score each time this repository was scanned.

Findings

Highest severity first. Select a finding to see the code and what it means.