Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add meltedinhex/analyst-ai-pack --skill analyzing-banking-trojan-webinjectsgit clone --depth 1 https://github.com/meltedinhex/analyst-ai-packWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/meltedinhex/analyst-ai-pack/analyzing-banking-trojan-webinjects)<a href="https://agentmods.dev/skills/meltedinhex/analyst-ai-pack/analyzing-banking-trojan-webinjects"><img src="https://agentmods.dev/badge/skills/meltedinhex/analyst-ai-pack/analyzing-banking-trojan-webinjects/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/meltedinhex/analyst-ai-pack/analyzing-banking-trojan-webinjects"><img src="https://agentmods.dev/badge/skills/meltedinhex/analyst-ai-pack/analyzing-banking-trojan-webinjects.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00071 | $0.00679 |
| Opus 5 | $0.00036 | $0.00340 |
| Sonnet 5 | $0.00014 | $0.00136 |
| Haiku 4.5 | $0.00007 | $0.00068 |
Grade A, and why
analyzing-banking-trojan-webinjects scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Analyzing Banking Trojan Webinjects
When to Use
- You have a banking trojan webinject config (Zeus/Gozi/Dridex-style
set_url/data_before/data_injectblocks) and want to extract targeted institutions and injected code. - You are mapping the web-fraud workflow (form-grabbing, fake fields, MFA interception).
Do not use this to deploy or test injects against live banking sites. This skill parses the config statically and executes nothing.
Prerequisites
- The decoded webinject config text (decrypt the config first if needed).
Safety & Handling
- Treat injected JS/HTML as malicious; do not render it. Defang any exfil URLs.
Workflow
Step 1: Parse webinject blocks
python scripts/analyst.py parse webinjects.txt
Parses set_url/data_before/data_inject/data_after blocks into structured entries with the
targeted URL pattern and the injected snippet.
Step 2: Extract targets and exfil endpoints
List targeted institution URL patterns and any exfil endpoints referenced by the injected code.
Step 3: Classify the injection technique
Identify form-grabbing, fake additional fields (SSN, PIN, card), and MFA/OTP interception from the injected markup/JS.
Step 4: Defang and report
Defang URLs and summarize targeted banks and theft techniques.
Validation
- Each webinject block is parsed into target URL + injection.
- Exfil endpoints in injected code are extracted and defanged.
- Injection techniques are classified from the snippet content.
Pitfalls
- Encrypted/packed configs needing decryption before parsing.
- Wildcard URL patterns matching broadly — note the scope.
- Obfuscated injected JS hiding the true exfil endpoint.
References
- See
references/api-reference.mdfor the parser. - ATT&CK T1185 and webinject format references (linked in frontmatter).
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 89 lines · 71 tokens per session scan A e643862f4f4c
analyzing-banking-trojan-webinjects is a skill published in the GitHub repository meltedinhex/analyst-ai-pack (22 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 71 tokens to every session and 679 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
analyzing-golang-malware-with-ghidra
Reverse engineer Go-compiled malware in Ghidra by parsing Go buildinfo and pclntab structures, recovering stripped/obfuscated function names (e.g. via GoResolver), and extracting embedded module/dependency strings and types from Go binaries. Use when analyzing a Go-language malware sample, deobfuscating a…
analyzing-malicious-pdf-with-peepdf
Perform static analysis of malicious PDF documents using peepdf, pdfid, and pdf-parser to extract embedded JavaScript, shellcode, and suspicious objects. Use when triaging a suspicious PDF attachment from a phishing email, analyzing a PDF-based exploit document, or building detection signatures for weaponized PDF…
analyzing-malicious-pdf-with-peepdf
A Chinese-language skill for examining suspicious PDF files with peepdf, pdfid, and pdf-parser. It is intended for static malware analysis, which studies a file without running it.
analyzing-malicious-pdf-with-peepdf
Perform static analysis of malicious PDF documents using peepdf, pdfid, and pdf-parser to extract embedded JavaScript, shellcode, and suspicious objects.
analyzing-malicious-pdf-with-peepdf
Perform static analysis of malicious PDF documents using peepdf, pdfid, and pdf-parser to extract embedded JavaScript, shellcode, and suspicious objects.
analyzing-malicious-pdf-with-peepdf
Perform static analysis of malicious PDF documents using peepdf, pdfid, and pdf-parser to extract embedded JavaScript, shellcode, and suspicious objects.