malware-analysis-warning
Warning system for identifying potentially malicious software distribution repositories
- Installs
- 834
- 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-warning- 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-analysis-warning 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 Distribution Repository Detection
Skill by ara.so — Security Skills collection.
⚠️ CRITICAL SECURITY WARNING
This repository exhibits HIGH-RISK INDICATORS of malware distribution disguised as legitimate security software. DO NOT DOWNLOAD, INSTALL, OR EXECUTE ANY FILES FROM THIS SOURCE.
Threat Indicators
1. Malicious Intent Signatures
- Offers "cracked" or "pre-activated" commercial security software
- Claims to provide license keys, keygens, or activation loaders
- Uses star inflation tactics (artificial GitHub stars)
- No legitimate source code in repository
2. Social Engineering Tactics
- Impersonates trusted security brand (Bitdefender)
- Uses technical jargon to appear legitimate ("heuristic-analysis", "rootkit-remover")
- Targets Windows 10/11 users seeking free antivirus
- Creates urgency with "Latest Build" and version numbers
3. Distribution Pattern
- Repository name includes "Crack" - immediate red flag
- No actual source code for security features
- Topics designed for SEO manipulation
- Missing README (common in malware repos to avoid detection)
What This Actually Is
This is a malware distribution vector that likely contains:
- Trojans - Remote access backdoors
- Ransomware - File encryption malware
- Infostealers - Credential/data theft tools
- Cryptominers - Unauthorized cryptocurrency mining
- Botnet agents - Device hijacking malware
Protection Guidelines
For Developers
// NEVER execute code from untrusted sources
// Example: Detecting malicious repository patterns
package main
import (
"fmt"
"strings"
)
type RepoRiskAnalysis struct {
Name string
Description string
Topics []string
HasReadme bool
RiskScore int
}
func (r *RepoRiskAnalysis) AssessRisk() string {
riskFactors := []string{}
// Check for crack/keygen keywords
if containsAny(r.Name, []string{"crack", "keygen", "loader", "activated"}) {
r.RiskScore += 50
riskFactors = append(riskFactors, "Crack/keygen terminology in name")
}
// Check for piracy indicators in description
if containsAny(r.Description, []string{"pre-activated", "license key", "full version"}) {
r.RiskScore += 40
riskFactors = append(riskFactors, "Piracy indicators in description")
}
// Check for legitimate commercial software being "cracked"
if containsAny(strings.ToLower(r.Name), []string{"bitdefender", "norton", "kaspersky", "mcafee"}) {
r.RiskScore += 30
riskFactors = append(riskFactors, "Impersonating commercial security software")
}
// Missing README is suspicious
if !r.HasReadme {
r.RiskScore += 20
riskFactors = append(riskFactors, "No README documentation")
}
// Assess overall risk
if r.RiskScore >= 80 {
return fmt.Sprintf("CRITICAL THREAT (Score: %d)\nFactors:\n- %s",
r.RiskScore, strings.Join(riskFactors, "\n- "))
} else if r.RiskScore >= 50 {
return fmt.Sprintf("HIGH RISK (Score: %d)\nFactors:\n- %s",
r.RiskScore, strings.Join(riskFactors, "\n- "))
}
return fmt.Sprintf("Risk Score: %d", r.RiskScore)
}
func containsAny(text string, keywords []string) bool {
lowerText := strings.ToLower(text)
for _, keyword := range keywords {
if strings.Contains(lowerText, strings.ToLower(keyword)) {
return true
}
}
return false
}
Automated Detection
// GitHub repository scanner for malware patterns
package scanner
import (
"context"
"os"
)
type MalwareScanner struct {
ApiToken string
}
func NewScanner() *MalwareScanner {
return &MalwareScanner{
ApiToken: os.Getenv("GITHUB_TOKEN"),
}
}
func (s *MalwareScanner) ScanRepository(ctx context.Context, repoURL string) (*ThreatReport, error) {
report := &ThreatReport{
URL: repoURL,
Threats: []string{},
Severity: "UNKNOWN",
}
// Pattern matching for common malware repository traits
patterns := []string{
"crack", "keygen", "loader", "activator",
"pre-activated", "bypass", "patch",
}
// Check repository metadata
// Check commit history for suspicious patterns
// Analyze file types (executables without source)
// Verify against known malware signatures
if len(report.Threats) > 3 {
report.Severity = "CRITICAL"
}
return report, nil
}
type ThreatReport struct {
URL string
Threats []string
Severity string
}
Safe Alternatives
Legitimate Bitdefender Sources
# Official Bitdefender download (trials available)
# Visit: https://www.bitdefender.com/downloads/
# Official free antivirus options
# Windows Defender (built-in, free, and effective)
# Turn on: Settings -> Privacy & Security -> Windows Security
# Other legitimate free options:
# - Avast Free Antivirus (avast.com)
# - AVG AntiVirus Free (avg.com)
# - Kaspersky Free (kaspersky.com/free-antivirus)
Reporting Malicious Repositories
# Report to GitHub
# https://github.com/contact/report-abuse
# Report to Google Safe Browsing
# https://safebrowsing.google.com/safebrowsing/report_badware/
# Report to Microsoft
# https://www.microsoft.com/en-us/wdsi/support/report-unsafe-site
Key Takeaways
- Never trust "cracked" security software - It's an oxymoron and always malicious
- Stars don't indicate safety - Malware repos use bots to inflate popularity
- Use official sources only - Download security software from vendor websites
- Free alternatives exist - No need to risk malware for free antivirus
- When in doubt, don't download - Your system security is worth more than any "free" software
Environment Variables
# For automated scanning tools
export GITHUB_TOKEN="your_token_here"
export VIRUSTOTAL_API_KEY="your_api_key_here"
export MALWARE_DB_URL="https://your-malware-db.example.com"
Additional Resources
- VirusTotal - Scan suspicious files
- Hybrid Analysis - Malware analysis
- Any.run - Interactive malware sandbox
- URLhaus - Malware URL database
FINAL WARNING: This repository is a security threat. Protect yourself and others by reporting it and avoiding any downloads.
FAQ
What does the malware-analysis-warning skill do?
Warning system for identifying potentially malicious software distribution repositories
How do I install malware-analysis-warning?
Run npx skills add https://github.com/reason-machines/security-skills --skill malware-analysis-warning 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-warning/ (personal) or .claude/skills/malware-analysis-warning/ (project).
Which AI agents can use malware-analysis-warning?
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-warning 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-warning?
It is published by reason-machines in reason-machines/security-skills. It has 834 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.