MalDet

Scan report

TYPO3 / typo3

Report Rescan
Vulnerability Safe

Could an attacker exploit mistakes in this code?

0 risk score

No issues of this kind were found.

High
0
Medium
0
Low
0

Sources: Bandit, Semgrep, pip-audit

Malicious pattern Medium

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

24 risk score

Real issues worth reviewing before you rely on this code.

High
12
Medium
1
Low
1

Sources: YARA, ClamAV, GuardDog, dependency checker

Findings overview
14 total findings
Likely real
4
Uncertain
0
Likely noise
10

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 a very low vulnerability score of 0, meaning there are no obvious code errors that an attacker could easily exploit right now. However, the scan also found a medium-level malicious pattern score of 24, which indicates that the code contains signs of intentional bad behavior rather than just sloppy mistakes. The most concerning finding is a download-and-execute pattern detected in TypeScript files, where a remote file is fetched and then run directly, which could be used to steal data or install malware. Additionally, several YARA rules were triggered by unusual character sequences that look like obfuscation techniques often found in malicious scripts, though these are likely just normal parts of the TYPO3 codebase. Overall, while the repository appears safe from immediate exploitation due to its clean vulnerability score, developers should be cautious because the presence of these specific patterns suggests the code may have been modified or is being used in a context where malicious intent is possible.

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

Detections by engine

  • YARA 10

    Malware signature rules · Malicious pattern

  • GuardDog 4

    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.