Scan report

HuskyHacks / PMAT-labs

Vulnerability Low

Could an attacker exploit mistakes in this code?

3 risk score

Minor issues. Worth a glance, unlikely to be urgent.

High
0
Medium
1
Low
0

Sources: Bandit, Semgrep, pip-audit

Malicious pattern Critical

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

346 risk score

Strong warning signs. Do not run or install this without a careful review.

High
43
Medium
0
Low
0

Sources: YARA, ClamAV, GuardDog, dependency checker

Findings overview
44 total findings
Likely real
34
Uncertain
2
Likely noise
8

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 shows two very different kinds of problems. The most serious issue is that the code contains malware signatures, including ransomware and trojans, which means the software could be used to steal data or damage systems if someone runs it. These malicious patterns are flagged by security tools with a critical score of 346.0, indicating a high likelihood that the code was intentionally created for harm rather than being a mistake. On the other hand, the developer's own codebase has only a low vulnerability risk score of 3.0, meaning it does not contain obvious insecure coding practices that an attacker could exploit from outside. This suggests that while the external code is dangerous, the internal logic used to generate or analyze it appears safe and follows standard security guidelines. In practice, you should treat this repository as unsafe for any production use because of the clear evidence of malicious intent in its source files.

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

Detections by engine

  • ClamAV 33

    Antivirus engine · Malicious pattern

  • YARA 10

    Malware signature rules · Malicious pattern

  • Semgrep 1

    Pattern-based code analysis · Vulnerability

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.