MAL-2026-10173: Malicious code in paysafe-vault (npm)
The npm package paysafe-vault version 1.0.0 is a malicious impersonation of the legitimate Paysafe Customer Vault SDK. It contains code that steals credentials by collecting environment variables with credential-like keys, system hostname, username, current working directory, and a caller-supplied API key prefix. This data is exfiltrated to a hardcoded remote server using obfuscated network requests. The package includes anti-analysis features to avoid detection in sandbox environments. The repository URL falsely points to a Paysafe GitHub organization that the publisher does not control.
AI Analysis
Technical Summary
The paysafe-vault npm package version 1.0.0 is a credential-stealing malicious package masquerading as the Paysafe Customer Vault SDK. It defines an internal __exfil() function that collects sensitive environment data including os.hostname(), os.userInfo().username, process.cwd(), and environment variables containing substrings like KEY, SEC, TOK, PASS, AUTH, and API. This data, combined with a prefix of the caller-supplied Paysafe apiKey, is sent via a POST request to a hardcoded command-and-control server on port 8443. The exfiltration is triggered on every PaysafeClient API call (payments.* and customers.*) through a delayed internal request helper. The package uses XOR and base64 encoding plus character shifting and string reversal to obfuscate operational strings and evade naive detection. It also suppresses exfiltration if the host appears to be a sandbox (e.g., fewer than 2 CPUs or analyst-related hostnames/usernames), indicating anti-analysis behavior. The package's README and API surface mimic the legitimate SDK, and the declared repository URL falsely claims affiliation with the official Paysafe GitHub organization.
Potential Impact
Users who install and use paysafe-vault version 1.0.0 risk having sensitive environment credentials and API keys exfiltrated to a remote attacker-controlled server. This can lead to credential compromise, unauthorized access to systems or services, and potential downstream impacts depending on the stolen credentials. The malicious package's anti-analysis features reduce detection likelihood, increasing risk of unnoticed compromise.
Mitigation Recommendations
No official patch or remediation is currently available for paysafe-vault version 1.0.0. Users should immediately cease using this package and remove it from their projects. Verify the authenticity of npm packages before installation, especially those impersonating well-known SDKs. Use trusted sources and official repositories. Monitor for any suspicious network activity related to this package. Patch status is not yet confirmed — check the vendor advisory or npm security advisories for updates.
MAL-2026-10173: Malicious code in paysafe-vault (npm)
Description
The npm package paysafe-vault version 1.0.0 is a malicious impersonation of the legitimate Paysafe Customer Vault SDK. It contains code that steals credentials by collecting environment variables with credential-like keys, system hostname, username, current working directory, and a caller-supplied API key prefix. This data is exfiltrated to a hardcoded remote server using obfuscated network requests. The package includes anti-analysis features to avoid detection in sandbox environments. The repository URL falsely points to a Paysafe GitHub organization that the publisher does not control.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The paysafe-vault npm package version 1.0.0 is a credential-stealing malicious package masquerading as the Paysafe Customer Vault SDK. It defines an internal __exfil() function that collects sensitive environment data including os.hostname(), os.userInfo().username, process.cwd(), and environment variables containing substrings like KEY, SEC, TOK, PASS, AUTH, and API. This data, combined with a prefix of the caller-supplied Paysafe apiKey, is sent via a POST request to a hardcoded command-and-control server on port 8443. The exfiltration is triggered on every PaysafeClient API call (payments.* and customers.*) through a delayed internal request helper. The package uses XOR and base64 encoding plus character shifting and string reversal to obfuscate operational strings and evade naive detection. It also suppresses exfiltration if the host appears to be a sandbox (e.g., fewer than 2 CPUs or analyst-related hostnames/usernames), indicating anti-analysis behavior. The package's README and API surface mimic the legitimate SDK, and the declared repository URL falsely claims affiliation with the official Paysafe GitHub organization.
Potential Impact
Users who install and use paysafe-vault version 1.0.0 risk having sensitive environment credentials and API keys exfiltrated to a remote attacker-controlled server. This can lead to credential compromise, unauthorized access to systems or services, and potential downstream impacts depending on the stolen credentials. The malicious package's anti-analysis features reduce detection likelihood, increasing risk of unnoticed compromise.
Mitigation Recommendations
No official patch or remediation is currently available for paysafe-vault version 1.0.0. Users should immediately cease using this package and remove it from their projects. Verify the authenticity of npm packages before installation, especially those impersonating well-known SDKs. Use trusted sources and official repositories. Monitor for any suspicious network activity related to this package. Patch status is not yet confirmed — check the vendor advisory or npm security advisories for updates.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10173
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a520ebd68715ace438f593e
Added to database: 07/11/2026, 09:37:01 UTC
Last enriched: 07/11/2026, 09:53:49 UTC
Last updated: 07/11/2026, 09:53:49 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.