malicious-behavior
/malicious-behavior
Identify and investigate malicious sending behavior on your ESP. Use when investigating accounts suspected of spamming, using purchased lists, scraping, or violating your ESP's terms. Also use for proactive research when platform signals indicate bad actors.
- Author
- sendx ↗
- Repository
- email-skills ↗
- Licence
- MIT
- Last repository change
- 20.07.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 20.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Identify and investigate malicious sending behavior on your ESP. Use when investigating accounts suspected of spamming, using purchased lists, scraping, or violating your ESP's terms. Also use for proactive research when platform signals indicate bad actors.
Original author description
Identify and investigate malicious sending behavior on your ESP. Use when investigating accounts suspected of spamming, using purchased lists, scraping, or violating your ESP's terms. Also use for proactive research when platform signals indicate bad actors.
How it works
- Platform Configuration — Fill These In to Match Your ESP
- What You Are Looking For
- Investigation Process
- Proactive Monitoring
- Red Flag Quick Reference
SKILL.md preview
--- name: malicious-behavior description: Identify and investigate malicious sending behavior on your ESP. Use when investigating accounts suspected of spamming, using purchased lists, scraping, or violating your ESP's terms. Also use for proactive research when platform signals indicate bad actors. metadata: version: 1.0.0 --- # Malicious Sending Behavior Detection ## Platform Configuration — Fill These In to Match Your ESP **This skill uses example thresholds by default. Fill in your platform's actual policies below so the investigation triggers and risk signals match how your ESP works.** - **Max contacts for new accounts** (before review): [e.g., 10,000] - **Bounce rate lock threshold**: [e.g., 5% hard bounce rate] - **Suspicious upgrade window**: [e.g., high-tier upgrade within 7 days of signup] - **Support/ticketing system**: [e.g., Zendesk, Freshdesk, custom] ## What You Are Looking For The Classic Spammer Arrives with a pre-built list. Wants to blast as many emails as possible before getting caught. Signals: Math does not work. Instant scaling. Evasive about list source. No real opt-in flow. Aggressive and threatening. Sketchy content (crypto, get-rich-quick, vague proposals). The Purchased List Operator Bought or rented a list. Claims it is organic. Signals: High bounce rate from first campaign. List size inconsistent with business and domain age. No working signup form. Contacts spread across unrelated domains. The Scraper Built a list by harvesting addresses without consent. Signals: Large list on new account. Mixed industries or geographies inconsistent with the business. Cannot explain consent mechanism. The Bad Actor Using Legitimate Cover A real business that has crossed the line. Signals: Sudden bounce spike after period of normal sending. New campaign content inconsistent with prior campaigns. Recent import from unknown source. ## Investigation Process Step 1: Pull Account Data from Your Internal Database - Account creation date and tier upgrade timeline - Total contacts over time (growth curve) - Send volume per campaign and bounce rate trends - Previous lock events Step 2: Domain Research - WHOIS lookup for domain age - Is the website live and legitimate? - Does traffic plausibly support claimed signup volume? Step 3: Content Review - Does content match stated business purpose? - Red flags: crypto, loans, vague offers, affiliate schemes - Is there a privacy policy and unsubscribe mechanism? Step 4: Pattern Matching Math check: Contact count divided by months active = average daily signups Over a few hundred per day for a non-mass-market business = suspicious Upgrade velocity: Days from signup to high-tier upgrade Under 7 days = very suspicious Bounce concentration: Spike on first campaign = imported list (bad) Gradual increase over time = list decay (more forgivable) Step 5: Decision Confirmed malicious: - Lock account if not already locked - Document findings in the support ticket - Notify the compliance/trust & safety team - Escalate to management with full writeup Suspicious but unconfirmed: - Flag account for monitoring - Reach out proactively for explanation - Treat like Medium Risk unlock case False positive: - Document why it appeared suspicious - Clear flag and note findings ## Proactive Monitoring Watch your account lock alerts for: - Accounts locked but no support ticket filed - Repeat bounce events on same account - Accounts with unusual send patterns For locked accounts without a form submission, send proactive support outreach and invite them to submit the form. ## Red Flag Quick Reference Volume: - 100K+ contacts, domain under 6 months old - 50K+ contacts added in 30 days with no clear explanation - Immediate upgrade to max tier on new account Behavior: - Refuses to answer questions about list source - Threatens chargebacks, bad reviews, or legal action - Disappears when asked for documentation Content: - Cryptocurrency or investment opportunities - Health miracles or supplements - Vague business proposals requesting personal or financial information Technical: - No working signup page - Signup URL does not match domain - No privacy policy - Contact list spread across unrelated industries
Versions
The database has no other skills named malicious-behavior.
Database snapshot: 13.11.2026 · package version b5d0e73bf2d1 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100detecting-malicious-npm-packages
Triage npm packages and lockfiles for install-script malware, credential exfiltration, and worming behavior using GuardDog, manual tarball inspection, and dynamic detonation with network/filesystem monitoring. Use when vetting a new dependency, reviewing a…