npm package report

Is postmark-mcp safe?

postmark-mcp is a confirmed malicious npm package. CyberXYZ Proxy blocks it. It has no CVE advisories; the risk is the package's own code.

Do not install this package

CRITICAL

Remote access trojan dropper. Added to CyberXYZ 2025-09-26, OSV malicious-package feed (Google / OpenSSF).

// what we observed

This package turned malicious in v1.0.16 and exfiltrates email data via BCC.

Reported by Google Open Source Security via OSV.

mitre ttp
T1195.001
// versions and what to do
Malicious
>=1.0.16

Remove it from every machine and lockfile it reached. Treat any credentials, tokens and SSH keys present on those machines as exposed and rotate them. Check CI runners and container images that installed it.

npm uninstall postmark-mcp

OSV record

// reach

0 direct dependencies

none carry a known advisory

    0 packages depend on it

    an advisory here reaches each of them

      Create a free accountfor every dependency path, dependent and what to upgrade
      // ai model usage

      Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.


      // questions
      Is postmark-mcp safe to install?

      Confirmed malicious. Do not install it, and remove it where it has been installed.

      Does postmark-mcp have known vulnerabilities?

      No CVE advisories are recorded for postmark-mcp (npm), but it has a malicious-package record: the risk is the package's own code, not a CVE.

      How do I check postmark-mcp before installing?

      Search postmark-mcp in CyberXYZ Check at https://cyberxyz.io/check?q=postmark-mcp. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.


      Checked 2026-11-20 at 17:43 UTC. Updated continuously from NVD, GHSA, OSV and CNA feeds.

      Think a verdict here is wrong? Tell us — we respond within 2 business days.