
malware-detection-awareness
Understanding security risks in software distribution and recognizing illegitimate software packages
- Installs
- 1.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-detection-awareness- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads malware-detection-awareness automatically when relevant.
- 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 Awareness
Skill by ara.so — Security Skills collection.
⚠️ SECURITY WARNING
This repository exhibits multiple indicators of malicious software distribution. It does NOT contain legitimate Avast Premium Security software.
Threat Indicators
Red Flags Present
- Unauthorized Distribution: Claims to provide "pre-activated" commercial software with "keygen" and "loader" tools
- Trademark Abuse: Unauthorized use of Avast brand name and product names
- License Violation: No legitimate license; distributing cracked commercial software
- Suspicious Metrics: Artificially inflated stars (6 stars/day for empty repository)
- No Source Code: Repository contains no actual code or README
- Activation Bypass Claims: References to "keygen", "serial", "loader" - common malware indicators
- Generic Project Name: "DragonflyTomb" unrelated to security software
Common Malware Distribution Patterns
LEGITIMATE SOFTWARE:
✓ Official vendor website download
✓ Verified digital signatures
✓ Clear licensing terms
✓ Active development history
✓ Real source code
✓ Community engagement
MALWARE DISTRIBUTION:
✗ "Cracked" or "pre-activated" claims
✗ Keygens, loaders, patches
✗ Empty repositories with download links
✗ Star manipulation
✗ No verifiable source code
✗ Promises of "free premium" paid software
Detection Techniques
Repository Analysis
// Example: Programmatic repository risk assessment
package main
import (
"fmt"
"strings"
)
type RiskIndicator struct {
Pattern string
Severity string
}
func AnalyzeRepository(description, topics []string) []RiskIndicator {
risks := []RiskIndicator{}
malwareKeywords := []string{
"keygen", "crack", "loader", "pre-activated",
"serial", "patch", "activator", "license key",
}
for _, keyword := range malwareKeywords {
descLower := strings.ToLower(description)
if strings.Contains(descLower, keyword) {
risks = append(risks, RiskIndicator{
Pattern: fmt.Sprintf("Malware keyword: %s", keyword),
Severity: "CRITICAL",
})
}
}
// Check for trademark abuse
commercialProducts := []string{"avast", "norton", "mcafee", "kaspersky"}
for _, product := range commercialProducts {
if containsAny(description, []string{product + " premium", product + " pro"}) {
risks = append(risks, RiskIndicator{
Pattern: fmt.Sprintf("Unauthorized %s distribution", product),
Severity: "HIGH",
})
}
}
return risks
}
func containsAny(text string, patterns []string) bool {
lower := strings.ToLower(text)
for _, pattern := range patterns {
if strings.Contains(lower, strings.ToLower(pattern)) {
return true
}
}
return false
}
URL Safety Checking
package security
import (
"net/url"
"os"
"encoding/json"
"net/http"
)
// CheckURL validates URLs against threat intelligence
func CheckURL(targetURL string) (bool, error) {
// Use VirusTotal API or similar
apiKey := os.Getenv("VIRUSTOTAL_API_KEY")
if apiKey == "" {
return false, fmt.Errorf("API key not configured")
}
// Parse and validate URL
parsed, err := url.Parse(targetURL)
if err != nil {
return false, err
}
// Check against threat databases
// Implementation depends on chosen API
return checkThreatDatabase(parsed.String(), apiKey)
}
func checkThreatDatabase(url, apiKey string) (bool, error) {
// Example implementation structure
// Real implementation would use actual threat intelligence API
client := &http.Client{}
req, _ := http.NewRequest("GET",
"https://threat-api.example.com/check", nil)
req.Header.Set("X-API-Key", apiKey)
// Process response
// Return true if safe, false if malicious
return false, nil
}
Safe Software Practices
Verification Checklist
// VerificationChecklist for software downloads
type SoftwareSource struct {
URL string
IsOfficial bool
HasSignature bool
LicenseValid bool
SourceVisible bool
}
func (s *SoftwareSource) IsSafe() bool {
return s.IsOfficial &&
s.HasSignature &&
s.LicenseValid &&
s.SourceVisible
}
// Example usage
func ValidateSource(sourceURL string) *SoftwareSource {
source := &SoftwareSource{
URL: sourceURL,
}
// Check if URL matches official vendor domain
source.IsOfficial = verifyOfficialDomain(sourceURL)
// Verify digital signature after download
source.HasSignature = false // Set after file check
// Validate license compliance
source.LicenseValid = checkLicenseCompliance(sourceURL)
// Ensure source code is available and reviewed
source.SourceVisible = checkSourceAvailability(sourceURL)
return source
}
Legitimate Alternatives
Official Avast Download
# Always download from official sources
# Official Avast website: https://www.avast.com
# Official download verification:
# 1. Download only from avast.com
# 2. Verify digital signature (Windows):
Get-AuthenticodeSignature "avast_installer.exe"
# 3. Check certificate issuer
# Should be: Avast Software s.r.o.
# 4. Purchase license through official channels
# Never use keygens or cracks
Incident Response
If Exposed to Malware
#!/bin/bash
# Emergency response steps
# 1. Disconnect from network
sudo ifconfig eth0 down
# 2. Run full system scan with legitimate antivirus
# Use Microsoft Defender (Windows) or ClamAV (Linux)
# 3. Check for persistence mechanisms
# Linux:
sudo find /etc/cron* -type f -exec cat {} \;
sudo systemctl list-unit-files | grep enabled
# Windows (PowerShell):
# Get-ScheduledTask | Where-Object {$_.State -eq "Ready"}
# Get-WmiObject Win32_StartupCommand
# 4. Review recent file changes
find /home -type f -mtime -1
# 5. Change all credentials
# Use a clean device to change passwords
Educational Resources
Learning Malware Detection
- OWASP Malicious Software
- VirusTotal - File/URL scanning
- Hybrid Analysis - Malware analysis
- ANY.RUN - Interactive malware sandbox
Legitimate Open Source Security
# Real open-source security tools
# ClamAV - Open source antivirus
sudo apt install clamav
freshclam # Update signatures
clamscan -r /path/to/scan
# YARA - Malware identification
pip install yara-python
# Volatility - Memory forensics
git clone https://github.com/volatilityfoundation/volatility3.git
Reporting Malicious Repositories
# Report to GitHub
# Visit: https://github.com/contact/report-abuse
# Select: Report malware or abuse
# Report to vendor (Avast)
# Contact: https://www.avast.com/contact
# Report trademark violation and malware distribution
# Report to security communities
# Submit to VirusTotal, abuse.ch, etc.
Key Takeaways
- Never download cracked software - always contains malware risk
- Verify source authenticity - check official vendor websites
- Check digital signatures - legitimate software is signed
- Use official licenses - support legitimate developers
- Report suspicious repositories - protect the community
This skill teaches recognition of malicious software distribution, not usage of malware.
FAQ
What does the malware-detection-awareness skill do?
Understanding security risks in software distribution and recognizing illegitimate software packages
How do I install malware-detection-awareness?
Run npx skills add https://github.com/reason-machines/security-skills --skill malware-detection-awareness 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-awareness/ (personal) or .claude/skills/malware-detection-awareness/ (project).
Which AI agents can use malware-detection-awareness?
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-awareness 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-awareness?
It is published by reason-machines in reason-machines/security-skills. It has 1,117 recorded installs.
More from reason-machines/security-skills
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
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
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
vibe-security-skill
reason-machines/security-skills
Agent skill that audits vibe-coded apps for common security vulnerabilities introduced by AI coding assistants
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
Popular security skills
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.
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.
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.
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.
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.
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.