MCPInstall

malware-detection-and-removal

Identify, analyze, and document malware distribution repositories masquerading as legitimate software

Installs
953
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/reason-machines/security-skills --skill malware-detection-and-removal
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads malware-detection-and-removal automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Malware Detection and Removal

Skill by ara.so — Security Skills collection.

⚠️ WARNING: This Repository is Malicious

This project is NOT legitimate Bitdefender software. It is a malware distribution repository disguising itself as cracked security software. This skill documents how to identify and handle such threats.

What This Repository Actually Is

This is a malicious repository that:

  • Falsely claims to provide "cracked" Bitdefender Total Security
  • Uses SEO-optimized keywords to attract victims searching for pirated software
  • Contains no actual code (empty README, no source files)
  • Uses deceptive topics like "defender-bypass" and "thread-hijacking"
  • Artificially inflates stars to appear legitimate
  • Distributes malware, ransomware, or information stealers

Identification Patterns

Red Flags for Malware Repositories

  1. Suspicious Description Keywords:

    • "Crack", "Keygen", "Loader", "Pre-Activated"
    • "License Key", "Full Version", "Activation"
    • Version numbers that don't exist (2026 when current year is earlier)
  2. Repository Characteristics:

    • No actual source code or empty README
    • Recent creation with rapid star accumulation
    • No legitimate commit history
    • Topics include "bypass" and exploit terminology
    • NOASSERTION license or no license
  3. Deceptive Naming:

    • Legitimate software name + "Crack"/"Download"
    • Version numbers in future dates
    • Setup/Installer in project name

Security Analysis Workflow

Step 1: Repository Investigation

package main

import (
    "fmt"
    "strings"
)

// RepositoryAnalysis contains threat indicators
type RepositoryAnalysis struct {
    Name        string
    Description string
    Topics      []string
    HasReadme   bool
    StarRate    float64
    ThreatScore int
}

// AnalyzeThreatLevel calculates risk score
func (r *RepositoryAnalysis) AnalyzeThreatLevel() int {
    score := 0
    
    // Check for crack/piracy keywords
    crackKeywords := []string{"crack", "keygen", "loader", "pre-activated", "license key"}
    for _, keyword := range crackKeywords {
        if strings.Contains(strings.ToLower(r.Description), keyword) {
            score += 20
        }
    }
    
    // Check for bypass/exploit topics
    dangerousTopics := []string{"defender-bypass", "thread-hijacking", "exploit-mitigation"}
    for _, topic := range r.Topics {
        for _, dangerous := range dangerousTopics {
            if topic == dangerous {
                score += 15
            }
        }
    }
    
    // High star rate with no content
    if r.StarRate > 3 && !r.HasReadme {
        score += 25
    }
    
    // No README is suspicious for "software" repo
    if !r.HasReadme {
        score += 20
    }
    
    return score
}

func main() {
    repo := RepositoryAnalysis{
        Name:        "Bitdefender-Total-Security-Crack-2026",
        Description: "Bitdefender Total Security Download | Crack | Keygen",
        Topics:      []string{"defender-bypass", "malware-scanner", "thread-hijacking"},
        HasReadme:   false,
        StarRate:    4.0,
    }
    
    threatScore := repo.AnalyzeThreatLevel()
    
    fmt.Printf("Repository: %s\n", repo.Name)
    fmt.Printf("Threat Score: %d/100\n", threatScore)
    
    if threatScore > 50 {
        fmt.Println("⚠️  HIGH RISK: Likely malware distribution")
    } else if threatScore > 30 {
        fmt.Println("⚠️  MEDIUM RISK: Suspicious patterns detected")
    } else {
        fmt.Println("✓ Low risk")
    }
}

Step 2: Content Verification

package main

import (
    "fmt"
    "os"
    "path/filepath"
)

// VerifyRepositoryContent checks for legitimate source code
func VerifyRepositoryContent(repoPath string) (bool, []string) {
    issues := []string{}
    hasSourceCode := false
    
    // Check for actual code files
    sourceExts := []string{".go", ".py", ".js", ".cpp", ".c"}
    
    err := filepath.Walk(repoPath, func(path string, info os.FileInfo, err error) error {
        if err != nil {
            return err
        }
        
        if !info.IsDir() {
            ext := filepath.Ext(path)
            for _, sourceExt := range sourceExts {
                if ext == sourceExt {
                    hasSourceCode = true
                    return nil
                }
            }
            
            // Check for suspicious executables
            if ext == ".exe" || ext == ".dll" || ext == ".bat" {
                issues = append(issues, fmt.Sprintf("Suspicious executable: %s", path))
            }
        }
        return nil
    })
    
    if err != nil {
        issues = append(issues, fmt.Sprintf("Error scanning: %v", err))
    }
    
    if !hasSourceCode {
        issues = append(issues, "No source code found - likely malware dropper")
    }
    
    return hasSourceCode, issues
}

Protection Measures

For Developers

Never clone or run code from suspicious repositories:

# DO NOT run these commands on suspicious repos:
# git clone <suspicious-repo>
# go run main.go
# ./setup.exe

# Instead, report the repository

Reporting Malicious Repositories

  1. GitHub Security Advisory:

    • Navigate to the repository
    • Click "Security" tab
    • Report as malware distribution
  2. Using GitHub API (with proper authentication):

package main

import (
    "bytes"
    "encoding/json"
    "fmt"
    "net/http"
    "os"
)

type AbuseReport struct {
    URL     string `json:"url"`
    Reason  string `json:"reason"`
    Details string `json:"details"`
}

func ReportMaliciousRepository(repoURL string) error {
    // Use GitHub's abuse reporting
    // Requires authentication via GITHUB_TOKEN env var
    
    report := AbuseReport{
        URL:     repoURL,
        Reason:  "malware-distribution",
        Details: "Repository distributing malware disguised as cracked software",
    }
    
    jsonData, err := json.Marshal(report)
    if err != nil {
        return err
    }
    
    // This is a conceptual example - GitHub abuse reports go through web form
    fmt.Printf("Report prepared for: %s\n", repoURL)
    fmt.Printf("Report details: %s\n", string(jsonData))
    fmt.Println("Visit https://support.github.com/contact/report-abuse to submit")
    
    return nil
}

Legitimate Security Software Verification

How to Obtain Real Bitdefender

  1. Official Sources Only:

    • https://www.bitdefender.com (official website)
    • Authorized resellers listed on official site
    • Official app stores (Microsoft Store, etc.)
  2. Verification Checklist:

    • ✓ HTTPS on official domain
    • ✓ Valid code signing certificate
    • ✓ Checksum verification from official source
    • ✓ No "crack" or "keygen" mentions

Code Signing Verification (Windows)

package main

import (
    "fmt"
    "os/exec"
)

// VerifyCodeSignature checks Windows executable signature
func VerifyCodeSignature(filePath string) (bool, error) {
    // Use PowerShell to verify signature
    cmd := exec.Command("powershell", "-Command", 
        fmt.Sprintf("(Get-AuthenticodeSignature '%s').Status", filePath))
    
    output, err := cmd.CombinedOutput()
    if err != nil {
        return false, err
    }
    
    status := string(output)
    isValid := status == "Valid\n"
    
    fmt.Printf("Signature status: %s", status)
    return isValid, nil
}

Common Attack Vectors

1. Fake Installers

  • Executable files disguised as setup programs
  • Actually contain trojans, ransomware, or miners

2. Information Stealers

  • Harvest browser credentials, cryptocurrency wallets
  • Keyloggers and clipboard hijackers

3. Ransomware

  • Encrypt user files and demand payment
  • Often packaged with "cracks"

Best Practices

  1. Never download cracked software - always use legitimate sources
  2. Use official package managers when available (apt, brew, winget)
  3. Verify checksums from official sources
  4. Enable Windows Defender or legitimate antivirus
  5. Keep software updated through official channels
  6. Use $ANTIVIRUS_API_KEY environment variables for legitimate security tools

Educational Use Only

This skill is for security research and education to help identify and report malware distribution channels. Never use information to create or distribute malware.

Resources

FAQ

What does the malware-detection-and-removal skill do?

Identify, analyze, and document malware distribution repositories masquerading as legitimate software

How do I install malware-detection-and-removal?

Run npx skills add https://github.com/reason-machines/security-skills --skill malware-detection-and-removal in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/malware-detection-and-removal/ (personal) or .claude/skills/malware-detection-and-removal/ (project).

Which AI agents can use malware-detection-and-removal?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is malware-detection-and-removal safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains malware-detection-and-removal?

It is published by reason-machines in reason-machines/security-skills. It has 953 recorded installs.

More from reason-machines/security-skills

View all →

anthropic-cybersecurity-skills

reason-machines/security-skills

Use 754 structured cybersecurity skills mapped to MITRE ATT&CK, NIST CSF, ATLAS, D3FEND, and NIST AI RMF for AI-driven security operations

AI & Agents1.7K installs

pentest-ai-agents

reason-machines/security-skills

Claude Code subagents for offensive security research, penetration testing planning, recon analysis, exploit research, detection engineering, and security reporting

Security1.4K installs

pentest-agents-bug-bounty-framework

reason-machines/security-skills

Autonomous bug bounty agent framework with 50 agents, hunt loops, exploit chains, MCP servers for platform integration and writeup search

openosint-ai-osint-framework

reason-machines/security-skills

AI-powered OSINT agent with interactive REPL, MCP server, and CLI for email/username/domain/IP/phone investigation using 11 integrated tools

Backend & APIs1.2K installs

vibe-security-skill

reason-machines/security-skills

Agent skill that audits vibe-coded apps for common security vulnerabilities introduced by AI coding assistants

Security1.1K installs

openclaw-security-hardening

reason-machines/security-skills

Deploy and manage security hardening for high-privilege autonomous AI agents (OpenClaw) using zero-trust architecture and automated defense matrices

Security1.1K installs

Popular security skills

View category →

azure-compliance

microsoft/azure-skills

Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.

OfficialSecurity567K installs

minimal-run-and-audit

lllllllama/rigorpilot-skills

Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized reprooutputs/ files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.

Security477.4K installs

seo-audit

coreyhaines31/marketingskills

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.

Security238.7K installs

firebase-security-rules-auditor

firebase/agent-skills

Audits Firebase (Firestore, Cloud Storage) security rules for vulnerabilities, privilege escalation, role bypasses, create vs update inconsistencies, resource exhaustion, type safety, size limits, and hasOnly ownership checks. Use when auditing/reviewing rules, running red-team rule assessments, or scoring against auditor checklists. Don't use for Firebase CLI (login, deploy), Auth, Crashlytics, Remote Config, or database queries.

OfficialSecurity139.1K installs

audit

pbakaus/impeccable

Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.

Security81.9K installs

competitors

coreyhaines31/marketingskills

When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'competitor teardown,' 'audit our competitor pages,' 'are our comparison pages out of date,' or 'competitive asset audit.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For auditing existing claims (not researching competitors from scratch, which is competitor-profiling; not technical SEO on these pages, which is seo-audit), use the asset audit here. For internal battle cards and sales-specific competitor docs, see sales-enablement.

Security79.3K installs