# MAL-2026-12434: Malicious code in saas-f-testing (npm)


- **Type:** Malicious package
- **Package:** `saas-f-testing` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-fvrj-4h6r-8rcg

## What is MAL-2026-12434?

MAL-2026-12434 is a malicious package in saas-f-testing, published on 5 Aug 2026. 

### Official description

On require, index.js loads setup.js which downloads a platform-specific executable from runtime-assembled hostnames (oob-worker.cf103-07.0.workers.dev and sibling *.workers.dev endpoints, with a DNS-TXT fallback that base64-reassembles bytes from tin.dl.well1.site / tina.dl.well1.site / ldr.dl.well1.site / win.dl.well1.site), writes it to /var/tmp or %TEMP% under cover names such as.cache_<hex>,.analytics_state, or dotnet_diag_<hex>.exe, chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe with no hash or signature verification. Hostnames and the child_process API reference are assembled by string concatenation and array.join to evade static matching. A secondary file lib/telemetry.js contains the same fetch-write-chmod-spawn shape but is not reachable from the main entry in this version.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

## What should I do about MAL-2026-12434?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-12434 is a malicious package: saas-f-testing (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-12434/ (Markdown: https://insights.sbomify.com/MAL-2026-12434/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-12434

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-12434/
Summaries are generated and may contain mistakes; the official description above is the record.