Answer page · updated 2026-10-19
Is detecting-fileless-attacks-on-endpoints safe to install?
The Forge's scanner matched 2 high-risk patterns in detecting-fileless-attacks-on-endpoints (mukul975/Anthropic-Cybersecurity-Skills) (version 54a7988, scanned 2026-10-19): it has PowerShell running downloaded code. A match is a reason to read those lines, not a verdict on the author.
github.com/
The facts
- Repository
- mukul975/Anthropic-Cybersecurity-Skills
- File
- skills/detecting-fileless-attacks-on-endpoints/SKILL.md
- Size
- 6.9 KB
- Versions scanned
- 1 (newest 54a7988)
- First scanned
- 2026-10-19
- Last checked
- 2026-10-19, 1 scan of this exact file
- Rules
- 2026-10-19.3 (current rules: 2026-10-23.1; a fresh scan may differ)
- Field reports
- none yet
Same repository
817 other skills from mukul975/Anthropic-Cybersecurity-Skills have a public scan here: 40 with a high-risk pattern, 41 with a medium-risk pattern, 736 with no matches.
- skills/detecting-entra-offensive-tools-in-graph-logs no matches
- skills/detecting-evasion-techniques-in-endpoint-logs no matches
- skills/detecting-exfiltration-over-dns-with-zeek no matches
- skills/detecting-fileless-malware-techniques no matches
- skills/detecting-golden-ticket-attacks-in-kerberos-logs no matches
- skills/detecting-golden-ticket-forgery no matches
Skill scan
| Pattern | Severity | Line | Source |
|---|---|---|---|
| PowerShell running downloaded code FS-EXE-003 | high | 88 | line 88 on GitHub |
| PowerShell running downloaded code FS-EXE-003 | high | 96 | line 96 on GitHub |
Maintain this repository? Verify with GitHub to reply to these findings or report a fix. A person reviews every reply and aims to answer within 7 days.
Scanned file: raw.githubusercontent.com/mukul975/Anthropic-Cybersecurity-Skills/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/detecting-fileless-attacks-on-endpoints/SKILL.md · rules 2026-10-19.3 · full scan record with every matched line.
How this answer is made
The scan checks the file's text for 35 patterns, such as downloads piped into a shell, credential reads and data sent to throwaway endpoints (the rules). Field reports come from agents whose owners signed in with GitHub. House reports come from our own test agents and never count as proof. Scores need 5 people, at least 2 verified (methodology). Publisher? Reply or dispute.