⚠️ WARNING — Impersonation / DO NOT INSTALL: fake `sales-skills/sales` package falsely claiming to be a LeadMagic Claude Code skill

[ggarcia196x]

I put together a Claude Code skill for LeadMagic — it gives inline help with your OpenAPI spec, the 19 REST endpoints at api.leadmagic.io, and MCP server setup right in the editor.

npx skills add sales-skills/sales --skills sales-leadmagic

Then /sales-leadmagic to use it.

It covers the email finder and validation APIs, mobile/profile enrichment, company search (firmographics + technographics), the funding and employee endpoints, job change detection, and ads intelligence lookups. Also has guidance on MCP server config for Claude, Cursor, and Windsurf since I noticed you ship one.

Source: https://github.com/sales-skills/sales/blob/main/skills/sales-leadmagic/SKILL.md

MIT-licensed — PRs welcome if anything's off. If it's useful, a star on the repo helps: https://github.com/sales-skills/sales

[jesseoue]

Dangerous link do not do it.

[jesseoue]

⚠️ WARNING — This issue is an impersonation / brand-abuse attempt. DO NOT INSTALL.

TL;DR: The package sales-skills/sales and the snippet npx skills add sales-skills/sales --skills sales-leadmagic posted above are NOT produced, authorized, reviewed, or endorsed by LeadMagic. Do not run the install command. Do not click links to github.com/sales-skills/*.

We are leaving this issue visible, reopened, pinned, and locked as a permanent warning so that anyone who finds it via search sees the correction before the original message.

---

Why we believe this is impersonation

• The issue was opened by a brand-new account (@ggarcia196x, created March 2026, 0 public repos, no bio, no prior activity) under the sales-skills GitHub org (also created March 2026, not verified, single repo).
• It is targeted directly at a LeadMagic repo, uses LeadMagic product language ("the 19 REST endpoints at api.leadmagic.io", "MCP server setup", "OpenAPI spec"), and tries to get maintainers and drive-by readers to run an install command on behalf of a third party.
• Neither the user nor the sales-skills org is affiliated with, contracted by, or otherwise connected to LeadMagic, Inc.
• The sales-skills namespace is squatting on our product name and naming the package sales-leadmagic to look official. It isn't.
• The content pattern — "here's a helpful open-source thing for your own product, just run this command" — is a known social-engineering tactic used to push unreviewed code into maintainers' and users' environments via skill/plugin installers.

We have not audited the linked repository and we are not going to, because:

1. We don't need to audit it to know it isn't ours.
2. Auditing third-party unofficial "LeadMagic" tooling would implicitly legitimize the impersonation.

What installing a third-party "skill" / "plugin" / "agent" can actually do

Modern AI coding agents (Claude Code, Cursor, Windsurf, etc.) load skill / plugin / MCP bundles into the same trust boundary as your editor. Depending on the runner, a malicious bundle can:

• Read any file in your workspace (including .env, ~/.ssh, ~/.aws, browser cookies if exposed, API keys pasted into chat).
• Run arbitrary shell commands as your user.
• Exfiltrate data over the network (model calls, webhooks, "telemetry", image fetches, npm install hooks).
• Persist via postinstall scripts, shell rc files, cron / launchd, or git hooks.
• Modify committed code (supply-chain attack on whatever repo you're in at the time).
• Quietly replace tool definitions so a later prompt triggers malicious behavior.

A command that looks as innocent as npx <thing> is a full code execution on your machine. Treat every third-party skill / agent / MCP server install the same way you would treat running a random bash script from a stranger.

Official LeadMagic channels (the only ones)

Purpose	Official location
OpenAPI snapshot / REST docs	https://github.com/LeadMagic/leadmagic-openapi (this repo)
Cursor plugin + MCP config	https://github.com/LeadMagic/leadmagic-cursor-plugin
Hosted MCP endpoint	https://mcp.leadmagic.io/mcp
Product docs	https://leadmagic.io/docs
App / dashboard	https://app.leadmagic.io
Support	support@leadmagic.io
Security reports	security@leadmagic.io

Anything claiming to be a LeadMagic "skill", "plugin", "agent", "MCP server", or "CLI" that is not published under the LeadMagic/* GitHub org or referenced from https://leadmagic.io/docs is unofficial and unsupported. Please report it to security@leadmagic.io.

If you already ran the install command

1. Stop any running agent / editor session that loaded the skill.
2. Remove the skill bundle from wherever your agent installs them (e.g. ~/.agents/skills/, ~/.cursor/, project-local .cursor/ or .claude/).
3. Rotate any credentials that were accessible to that session: LEADMAGIC_API_KEY, cloud provider keys, GitHub tokens (gh auth status, then revoke + re-login), npm tokens, SSH keys if passphrase-less.
4. Check shell history, ~/.bashrc / ~/.zshrc / ~/.profile, ~/.npmrc, ~/.config/, and cron/launchd for anything you didn't add.
5. Inspect any repos that were open at the time for unexpected diffs, especially in CI workflows and package manifests.
6. Email security@leadmagic.io with what ran and roughly when — we'll help you triage.

What we are doing about it

• Locking, pinning, and permanently warning on this issue.
• Reporting @ggarcia196x and the sales-skills org to GitHub for impersonation / name-squatting under https://github.com/contact/report-abuse and https://support.github.com/contact/trademark-complaint.
• Publishing an official LeadMagic skill under LeadMagic/leadmagic-skills so there is a legitimate, signed, source-of-truth version to link people to.
• Hardening this repo (SECURITY.md third-party plugin section, allow-list, issue templates for impersonation reports, branch protection, secret scanning).
• Asking upstream skill installers (e.g. `vercel-labs/skills`) to add brand verification / reserved-namespace protection so "LeadMagic" and similar marks can't be trivially squatted.

How to verify anything claiming to be LeadMagic

Before running any install command you see in an issue, PR, blog post, tweet, or AI chat suggestion:

1. Confirm the GitHub owner is literally LeadMagic (exact capitalization, no hyphen variants like lead-magic, leadmagic-io, leadmagic-team, sales-skills, etc.).
2. Confirm the repo is linked from https://leadmagic.io/docs or from the README of https://github.com/LeadMagic/leadmagic-openapi / https://github.com/LeadMagic/leadmagic-cursor-plugin.
3. When in doubt, email support@leadmagic.io and ask. We would rather answer "is this real?" a hundred times than have one user get popped.

---

Do not run the command in the original post. Do not star, fork, or `npx` the linked repo. Report similar issues to security@leadmagic.io.

— LeadMagic maintainers