Seventeen Fake Payment SDKs: The npm and PyPI Paysafe Campaign and Why Registry Malware Is Now a Compliance Problem, Not Just a Security One

2026-07-08 · Source: Global Privacy Laws & Compliance Frameworks | ComplianceHub.Wiki · Field: Technology & Digital — Cybersecurity & Data Privacy, Software Development & Engineering, Compliance & Risk Management · Depth: Intermediate, long

Summary

On July 7, 2026, a threat actor published 17 malicious packages—13 on npm and 4 on PyPI—impersonating official SDKs for Paysafe, Skrill, and Neteller. These fake SDKs, including "paysafe-node" and "skrill-sdk", appeared functional, returning "{ success: true }" responses without contacting payment platforms. Instead, they harvested API keys, AWS credentials, GitHub and npm tokens, and other environment variables, exfiltrating data via HTTPS to an ngrok tunnel. Socket's AI scanner detected the npm cluster within six minutes. This campaign exploited unclaimed package names on public registries, targeting developers building payment functionality whose environments hold high-value credentials. The article highlights that such incidents are now compliance failures under regulations like the EU Cyber Resilience Act, NIS2, PCI DSS 4.0, and US federal secure software attestation, not just security issues.

Key takeaway

For Engineering and Compliance Leads managing software supply chains, this campaign underscores that unvetted public-registry components are now a significant compliance liability. You must implement controls like internal registry proxies, mandatory lockfiles, and scoped CI secrets to prevent similar attacks. Failing to generate queryable SBOMs and verify component provenance exposes your organization to severe regulatory penalties under CRA, NIS2, and PCI DSS 4.0, and risks false attestation under US federal regimes. Proactively register your brand's package names.

Key insights

Unclaimed package names on public registries enable sophisticated brand impersonation, turning developer installs into compliance risks.

Principles

• Public registries lack strong identity guarantees.
• Payment brands are high-value targets.
• CI/CD environments concentrate secrets.

Method

Malicious SDKs mimic legitimate functionality, harvest environment variables (KEY, SECRET, TOKEN, PASS, AUTH, API), fingerprint hosts, exfiltrate data via obfuscated ngrok tunnels, and evade analysis environments.

In practice

• Implement registry allow-listing via internal proxies.
• Pin and lock all dependencies with lockfiles.
• Isolate CI secrets to specific jobs.

Topics

• Software Supply Chain Security
• Registry Malware
• Payment SDKs
• npm Security
• PyPI Security
• EU Cyber Resilience Act
• SBOM

Best for: CTO, VP of Engineering/Data, Executive, Security Engineer, Software Engineer, Legal Professional

Related on AIssential

• Popular Codex package caught exfiltrating authentication credentials — Malicious npm packages can embed credential exfiltration, exploiting trust and persistent tokens for indefinite access.
• Uncovering Similar but Different Packages in PyPI and Potential Security Threats — PyPI package replication creates significant security blind spots and facilitates malware distribution.
• Linux explores new way of authenticating developers and their code - here's how it works — Linux ID replaces PGP with decentralized identifiers and verifiable credentials for robust open-source identity verification.
• Microsoft Hacked to Deliver Malware to Claude and Gemini Users — Microsoft's GitHub repositories were compromised to deliver credential-stealing malware to AI coding agent users.
• Valid certificates, stolen accounts: how attackers broke npm's last trust signal — Automated trust signals in developer tools are broken by credential theft and design flaws, enabling widespread supply chain attacks.
• Our response to the TanStack npm supply chain attack — Supply chain attacks targeting open-source dependencies pose a significant and evolving threat to modern software ecosystems.

See Counsel's argued verdicts on the open AI decisions leaders are weighing →

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by Global Privacy Laws & Compliance Frameworks | ComplianceHub.Wiki.