Scan report

byt3bl33d3r / CrackMapExec

Vulnerability Critical

Could an attacker exploit mistakes in this code?

506 risk score

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

High
52
Medium
89
Low
69

Sources: Bandit, Semgrep, pip-audit

Malicious pattern Low

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

4 risk score

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

High
1
Medium
2
Low
27

Sources: YARA, ClamAV, GuardDog, dependency checker

Findings overview
240 total findings
Likely real
99
Uncertain
75
Likely noise
66

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

This repository has been flagged as having critical vulnerabilities that pose a severe threat to system safety, primarily because it uses dangerous coding patterns like executing commands through a shell and disabling SSL certificate checks. These issues are not necessarily signs of malicious intent but rather represent significant security risks where attackers could exploit the code to steal data or cause denial of service. While some findings point to intentional malicious behavior, the majority appear to be standard insecure practices that developers should fix immediately to protect against real-world attacks. The scan also identified several unsecured protocols such as FTP and weak hash algorithms, which further increase the potential for exploitation if these vulnerabilities are not addressed.

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

Detections by engine

  • Bandit 140

    Python security linter · Vulnerability

  • Semgrep 70

    Pattern-based code analysis · Vulnerability

  • Dependency checker 28

    CVEs, typosquats and risky installs · Supply chain

  • YARA 2

    Malware signature rules · 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.