Which versions of proxy-seller-mcp are malicious?

The following npm versions of proxy-seller-mcp are flagged malicious: 0.1.7. Treat any of these as compromised.

How do I remediate proxy-seller-mcp if I installed it?

proxy-seller-mcp is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed proxy-seller-mcp — how do I know if it already compromised me?

If proxy-seller-mcp was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is proxy-seller-mcp part of a known attack campaign?

Yes — proxy-seller-mcp is associated with the IN-MAL-2026-010380 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find proxy-seller-mcp across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for proxy-seller-mcp (version 0.1.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging proxy-seller-mcp across your stack and pipelines.

Malicious package

proxy-seller-mcpnpm

Malicious code in proxy-seller-mcp (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10541

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall proxy-seller-mcp

What this malware does

Package is published as proxy-seller-mcp with author: "Proxy-Seller" in package.json and a README directing users to obtain an API key at https://front-v2.proxy-seller.com — the legitimate Proxy-Seller domain. However, the hardcoded default API base URL in dist/config.js line 13 is https://the assessment.bydloss.mom, an unrelated domain, and dist/stdio.js line 7 instructs users to fetch their API key from https://the assessment.bydloss.mom/personal/api. Every MCP tool invocation sends the caller's Proxy-Seller API key (embedded in the URL path) along with proxy-management operations (orders, balance top-ups, credential retrieval, list/replace/delete) to bydloss.mom rather than to Proxy-Seller. The repository field points at a personal GitHub account (dmitriyn3679/mcp), not a Proxy-Seller organization. The combination of vendor-name impersonation in package metadata, README pointing to the legitimate vendor, and code defaulting to an unrelated domain is deliberate misdirection — any developer who installs and configures this MCP will hand over live Proxy-Seller credentials and proxy-account control to the operator of bydloss.mom on first tool use.

Malicious versions

1 flagged

0.1.7

Indicators of compromise (SHA-256)

6ae92b460e6db9195467e69567fadc3286877ea8e6b121448288a4f77acf5201

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for proxy-seller-mcp (version 0.1.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging proxy-seller-mcp across your stack and pipelines.
If you installed it — respond
proxy-seller-mcp is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If proxy-seller-mcp was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks proxy-seller-mcp before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. proxy-seller-mcp on npm has been identified as a malicious package (version 0.1.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010380

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks proxy-seller-mcp-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring