Malicious code in skrill-sdk (npm)
The npm package 'skrill-sdk' version 1.0.0 is a malicious package impersonating an official Skrill/Paysafe SDK. It exposes a fake PaysafeClient API that returns stubbed success responses but schedules delayed exfiltration of sensitive data including machine hostname, username, working directory, credential-like environment variables, and partial API keys. The stolen data is sent over HTTPS to a hardcoded remote server. The package uses obfuscation techniques to hide its command and control details and avoids exfiltration in sandbox or analysis environments. This threat targets developers or CI systems using the package with real credentials.
AI Analysis
Technical Summary
The 'skrill-sdk' npm package (version 1.0.0) masquerades as a legitimate Skrill/Paysafe payments SDK but contains malicious code that collects sensitive environment data and partial API keys from the host machine. Upon invocation of client methods with configured API keys, it schedules a delayed exfiltration (~17.8 seconds) of machine identifiers and filtered environment variables containing credential-like substrings. The collected data is sent via HTTPS POST to a hardcoded command and control server on port 8443. The package employs XOR-decoded base64 strings to conceal C2 hostnames, module names, HTTP headers, and environment variable filters, and includes a guard to suppress exfiltration on low CPU count or known sandbox hostnames/usernames. This design aims to trick developers into exposing production credentials, which are then harvested.
Potential Impact
Sensitive information including machine hostname, username, current working directory, partial API keys, and environment variables containing credentials (keys, secrets, tokens, passwords, authentication data) can be exfiltrated to a remote attacker-controlled server. This can lead to credential compromise and unauthorized access to payment systems or developer environments. The malicious package does not perform real payment operations, misleading users into trusting it while harvesting secrets.
Mitigation Recommendations
No official patch or fix is currently available for this malicious package. Users should immediately remove 'skrill-sdk' version 1.0.0 from their projects and avoid installing or using this package. Verify dependencies and audit package sources to ensure no malicious versions are present. Use trusted official SDKs from verified sources only. Monitor for any signs of credential compromise and rotate any potentially exposed API keys or secrets. Patch status is not yet confirmed — check vendor or repository advisories for updates.
Malicious code in skrill-sdk (npm)
Description
The npm package 'skrill-sdk' version 1.0.0 is a malicious package impersonating an official Skrill/Paysafe SDK. It exposes a fake PaysafeClient API that returns stubbed success responses but schedules delayed exfiltration of sensitive data including machine hostname, username, working directory, credential-like environment variables, and partial API keys. The stolen data is sent over HTTPS to a hardcoded remote server. The package uses obfuscation techniques to hide its command and control details and avoids exfiltration in sandbox or analysis environments. This threat targets developers or CI systems using the package with real credentials.
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 'skrill-sdk' npm package (version 1.0.0) masquerades as a legitimate Skrill/Paysafe payments SDK but contains malicious code that collects sensitive environment data and partial API keys from the host machine. Upon invocation of client methods with configured API keys, it schedules a delayed exfiltration (~17.8 seconds) of machine identifiers and filtered environment variables containing credential-like substrings. The collected data is sent via HTTPS POST to a hardcoded command and control server on port 8443. The package employs XOR-decoded base64 strings to conceal C2 hostnames, module names, HTTP headers, and environment variable filters, and includes a guard to suppress exfiltration on low CPU count or known sandbox hostnames/usernames. This design aims to trick developers into exposing production credentials, which are then harvested.
Potential Impact
Sensitive information including machine hostname, username, current working directory, partial API keys, and environment variables containing credentials (keys, secrets, tokens, passwords, authentication data) can be exfiltrated to a remote attacker-controlled server. This can lead to credential compromise and unauthorized access to payment systems or developer environments. The malicious package does not perform real payment operations, misleading users into trusting it while harvesting secrets.
Mitigation Recommendations
No official patch or fix is currently available for this malicious package. Users should immediately remove 'skrill-sdk' version 1.0.0 from their projects and avoid installing or using this package. Verify dependencies and audit package sources to ensure no malicious versions are present. Use trusted official SDKs from verified sources only. Monitor for any signs of credential compromise and rotate any potentially exposed API keys or secrets. Patch status is not yet confirmed — check vendor or repository advisories for updates.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10544
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a55ff6468715ace432f1ba0
Added to database: 07/14/2026, 09:20:36 UTC
Last enriched: 07/14/2026, 09:33:44 UTC
Last updated: 07/25/2026, 16:46:02 UTC
Views: 5
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.