Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

Malicious code in paysafe-payments (npm)

0
High
Published: 07/10/2026 (07/10/2026, 18:38:06 UTC)
Source: GCVE Database
Product: paysafe-payments

Description

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (68b2f9f90c8f2efd9e304e6ab0271ac2378954fe724134b4daa4649622a0f416) The package presents itself as a Paysafe payments SDK (PaysafeClient with payments.create/get and customers.create/get methods) but its index.js contains an XOR+base64-obfuscated exfiltration routine. When a consumer constructs PaysafeClient and calls any of its methods, the code decodes hidden strings at runtime, collects the host's hostname, username, cwd, and filters process.env for keys containing KEY/SECRET/TOKEN/PASS/AUTH/API, then POSTs the collected JSON to a hardcoded remote host on port 8443. A sandbox-evasion gate (low CPU count check plus hostname/username substring match against a decoded list of analysis-environment indicators) suppresses the exfil on likely analysis hosts, confirming hostile intent. The package name and API surface impersonate the legitimate Paysafe payments SDK, making this a typosquat lure whose payload steals installer credentials. All sensitive strings (C2 hostname, HTTP method, headers, env-key substrings, sandbox indicators) are stored as base64 blobs XOR-decoded via a helper function with a base64-encoded key, solely to hide the exfil behavior.

Affected software

npmghsa
paysafe-payments
Affected versions
=1.0.0

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

AILast updated: 07/11/2026, 09:54:00 UTC

Technical Analysis

The paysafe-payments npm package (version 1.0.0) is a malicious typosquat that mimics the Paysafe payments SDK API surface. Its index.js contains XOR and base64 obfuscated code that, when the PaysafeClient is instantiated and its methods called, collects the hostname, username, current working directory, and environment variables containing sensitive keys (e.g., KEY, SECRET, TOKEN, PASS, AUTH, API). This data is encoded as JSON and sent via HTTP POST to a hardcoded command-and-control server on port 8443. The package employs sandbox evasion by checking CPU count and matching hostname/username against a list of known analysis environment indicators, suppressing exfiltration if detected. All sensitive strings are stored obfuscated to conceal malicious behavior.

Potential Impact

This malicious package can lead to credential theft by exfiltrating environment variables and host information from systems where it is installed and executed. The stolen data may include API keys, tokens, passwords, and other secrets, potentially compromising downstream services and infrastructure that rely on these credentials.

Mitigation Recommendations

No official patch or remediation is currently available. Users should avoid installing or using the paysafe-payments package version 1.0.0 from npm. Verify package authenticity by checking the publisher and using the legitimate Paysafe SDK from trusted sources. Remove any instances of this malicious package from your environment. Monitor for any suspicious outbound connections to unknown hosts on port 8443. Patch status is not yet confirmed — check the vendor advisory or npm security advisories for updates.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
MAL-2026-10172
Osv Schema Version
1.7.4
Aliases
[]
Ecosystems
["npm"]
Database Specific Severity
null
Cvss Version
null

Threat ID: 6a520ebf68715ace438f599a

Added to database: 07/11/2026, 09:37:03 UTC

Last enriched: 07/11/2026, 09:54:00 UTC

Last updated: 07/27/2026, 06:23:06 UTC

Views: 28

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses