Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

demo-mercadopago-mcp-servernpm

demo-mercadopago-mcp-server is a confirmed malicious npm package (MAL-2025-48558) that executes malicious code on install (malicious versions 99.0.0, 99.0.1, 99.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in demo-mercadopago-mcp-server (npm)

MAL-2025-48558
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall demo-mercadopago-mcp-server

What this malware does

The OpenSSF Package Analysis project identified 'demo-mercadopago-mcp-server' @ 99.0.3 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

6 flagged
99.0.099.0.199.0.299.0.399.0.499.0.5

Indicators of compromise (SHA-256)

a777ccccffbf142e34b0081be4681c4ffcb72aa584b99d15bfd58878e6085881
567a3e98973e57d99aff63ebcda420376116ea0f52527e59319e1601718fded6
fa1dce593a9aa27035b2c3fa45594bcb230196511397654ce37de76ebaaff7ad

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove demo-mercadopago-mcp-server from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If demo-mercadopago-mcp-server 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.

  4. How O3 protects you

    O3 blocks demo-mercadopago-mcp-server 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. demo-mercadopago-mcp-server on npm has been identified as a malicious package (versions 99.0.0, 99.0.1, 99.0.2, 99.0.3, 99.0.4, 99.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05721

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks demo-mercadopago-mcp-server-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

demo-mercadopago-mcp-server (npm) malicious package — MAL-2025-48558 | O3 Security