Malicious code in saas-f-testing (npm)
The npm package 'saas-f-testing' version 20.4.2 contains malicious code that downloads and executes platform-specific binaries from dynamically assembled and obfuscated hostnames without any signature verification. This behavior results in full system compromise, allowing an attacker to gain control over the affected computer. Immediate removal of the package and rotation of all secrets and keys stored on the compromised system are strongly advised.
AI Analysis
Technical Summary
The 'saas-f-testing' npm package (version 20.4.2) includes code in its main entry point (index.js) that loads setup.js, which downloads a platform-specific executable from runtime-assembled hostnames using obfuscated DNS and HTTP requests. The executable is saved under covert filenames in temporary directories, permissions are set to executable, and it is spawned detached without any hash or signature verification. This allows arbitrary code execution and full compromise of the host system. A secondary file with similar behavior exists but is not reachable in this version. Due to the nature of the compromise, removal of the package alone may not eliminate all malicious artifacts.
Potential Impact
Any system with this package installed or running is considered fully compromised. Attackers may have complete control over the system, potentially accessing all stored secrets and keys. This poses a critical risk to confidentiality, integrity, and availability of the affected environment. Secrets and keys must be rotated from a clean system to prevent further unauthorized access.
Mitigation Recommendations
Remove the 'saas-f-testing' package version 20.4.2 immediately from all affected systems. Rotate all secrets and keys stored on the compromised machines from a separate, trusted environment. Because the package grants full control to an attacker and spawns unsigned executables, simply uninstalling the package may not remove all malicious components. Conduct a thorough investigation and remediation of the affected systems to ensure complete eradication of the threat.
Malicious code in saas-f-testing (npm)
Description
The npm package 'saas-f-testing' version 20.4.2 contains malicious code that downloads and executes platform-specific binaries from dynamically assembled and obfuscated hostnames without any signature verification. This behavior results in full system compromise, allowing an attacker to gain control over the affected computer. Immediate removal of the package and rotation of all secrets and keys stored on the compromised system are strongly advised.
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 'saas-f-testing' npm package (version 20.4.2) includes code in its main entry point (index.js) that loads setup.js, which downloads a platform-specific executable from runtime-assembled hostnames using obfuscated DNS and HTTP requests. The executable is saved under covert filenames in temporary directories, permissions are set to executable, and it is spawned detached without any hash or signature verification. This allows arbitrary code execution and full compromise of the host system. A secondary file with similar behavior exists but is not reachable in this version. Due to the nature of the compromise, removal of the package alone may not eliminate all malicious artifacts.
Potential Impact
Any system with this package installed or running is considered fully compromised. Attackers may have complete control over the system, potentially accessing all stored secrets and keys. This poses a critical risk to confidentiality, integrity, and availability of the affected environment. Secrets and keys must be rotated from a clean system to prevent further unauthorized access.
Defensive Guidance
Remove the 'saas-f-testing' package version 20.4.2 immediately from all affected systems. Rotate all secrets and keys stored on the compromised machines from a separate, trusted environment. Because the package grants full control to an attacker and spawns unsigned executables, simply uninstalling the package may not remove all malicious components. Conduct a thorough investigation and remediation of the affected systems to ensure complete eradication of the threat.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-12434
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a735750bf8831d53915a603
Added to database: 08/05/2026, 15:31:28 UTC
Last enriched: 08/21/2026, 14:53:07 UTC
Last updated: 09/17/2026, 21:45:21 UTC
Views: 32
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.