# MAL-2026-17899: Malicious code in @flexmr/survey-conversation (npm)


- **Type:** Malicious package
- **Package:** `@flexmr/survey-conversation` (npm)
- **Published:** 16 Oct 2026
- **Also known as:** GHSA-hc8w-gq4q-fr74

## What is MAL-2026-17899?

MAL-2026-17899 is a malicious package in @flexmr/survey-conversation, published on 16 Oct 2026. 

### Official description

package.json declares its sole dependency `cache-format-syntax-tracer` as a bare HTTPS URL (`https://artifacts.creditslib.com/npm/cache-format-syntax-tracer`) rather than a registry version range. On `npm install`, npm fetches whatever bytes that host serves and executes any lifecycle scripts inside, with no version pin, no registry integrity check, and no hash. The shipped `index.js` is a one-line re-export of that dependency, so runtime behavior is also fully delegated to the externally-hosted bytes. Whoever controls `artifacts.creditslib.com` controls code on every installer's machine, and the content can change between installs without any change to this package. The package is published under the `@flexmr` scope with placeholder author/publisher metadata (`example/@flexmr/...`, `Package Registry`), consistent with a dependency-confusion lure targeting an internal `@flexmr` package name.

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-17899?

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-17899 is a malicious package: @flexmr/survey-conversation (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-17899/ (Markdown: https://insights.sbomify.com/MAL-2026-17899/index.md)
```

## Sources

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

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