Skip to main content
MalwarePublished Updated

@flexmr/survey-conversation (npm) · Malicious Code

Affects @flexmr/survey-conversationSource GCVE Database

0

Malicious package : remove @flexmr/survey-conversation and rotate any secrets on hosts that installed it.

Data as of 27 Oct 2026, 17:27 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-17899

What to do

Remove @flexmr/survey-conversation from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

ProductAffectedFixed in
npm@flexmr/survey-conversationAffected
  • 1.0.0 – 10.0.12
5 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (20ab57dd6ac5a0eafc23934f6e715064453641bc57a549050f1d2e66a7630374) 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. ## Source: ghsa-malware (b8f042afac9d9ae3889355bedbbe09987373e982aa49ccbc8a4bfceb8bc28416) 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.

References

Community reviews

Loading reviews…