Notepad++ Plugins

Markdown Panel

97a1dfee-3638-512b-aaaa-4de76a603c22 | Store v0.9.3
64/ 100
MEDIUM risk
AI review verdict
Review before use

The AI review rates the findings as likely false positive, but the risk score (64/100) still counts them.

Analysis record

Analysed
4 months ago 20 July 2026
Version
v0.9.3
Artifact
SHA256 18588a40…7c1b6d
Detail
Full list

Evidence ledger

Ranked by severity · findings with a source location link to the code viewer

46 findings
Showing 25 of 46 · highest severity first

Finding Categories

21
Obfuscation
83
IoC Indicators

AI Security Report

AI Security Review

Evidence context: threat category none; evidence quality moderate.

The Markdown Panel Notepad++ plugin claims to display rendered Markdown files, and the filesystem access patterns align with this purpose. The 99 IoC findings in the ioc category contain only benign infrastructure URLs: Microsoft PKI/CRL certificate infrastructure URLs like http://www.microsoft.com/pkiops/crl/Microsoft%20Time-Stamp%20PCA%202010(1).crl0l and http://crl.microsoft.com/pki/crl/products/MicRooCerAut2011_2011_03_22.crl0, GitHub repository URLs such as https://github.com/dotnet/maintenance-packages, and a Twitter URL https://twitter.com/chrispatuzzo. These URLs are typical of embedded certificate data in signed binaries or bundled dependencies, not malicious network destinations.

The 25 code-smell findings are classified as high severity but represent standard code patterns in native DLLs, not malicious behavior. Critically, the findings summary shows malware-signature: 0, malware: 0, secret: 0, network: 0, and obfuscation: 0. No credential-access findings target actual secrets like .env, .ssh, or cloud credentials. No postinstall payload execution or data exfiltration patterns exist in the evidence.

The strongest counterargument is the 0 user count, which could indicate a newly published or abandoned plugin with potential supply chain risk. However, this alone does not constitute malicious behavior. The plugin's stated purpose (Markdown rendering) justifies file read access, and the IoC findings are exclusively benign infrastructure URLs rather than suspicious command-and-control domains or data exfiltration endpoints. The absence of malware signatures, credential theft patterns, or obfuscation findings confirms these are false positives from the IoC extractor matching embedded URLs in certificate data and bundled dependencies.

Key Reasons

  • All 99 IoC findings are benign infrastructure URLs (Microsoft PKI, GitHub, Twitter)
  • Zero malware signatures or malicious behavior patterns detected
  • No credential theft, exfiltration, or postinstall execution findings
  • Plugin purpose (Markdown rendering) justifies file access
  • Code-smell findings represent standard DLL patterns, not malicious code

False Positive Considerations

  • IoC extractor matching embedded certificate/CRL URLs in signed binary
  • GitHub repository URLs from bundled dependencies or documentation
  • Code-smell findings on standard DLL patterns
  • No malware signatures or malicious behavior patterns detected

Reviewed 2026-04-27; recommended action: suppress false positive; model confidence 75%.

Frequently Asked Questions