GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

MAL-2026-17898unknown

Malicious code in @flexmr/survey-client (npm)

No CVE assignedReported malicious packageCheck your stack

The advisory, in context


-= Per source details. Do not edit below this line.=-

Source: amazon-inspector (ed5d0e26b18d32568569b828bdbe2ccb40d0c4a54780c6e51be6280cb5fc851f)

@flexmr/survey-client@10.0.12 declares its sole dependency 'marker-index-symbol-schema' as a bare HTTPS URL to https://artifacts.creditslib.com/npm/marker-index-symbol-schema instead of a registry version range. On npm install, npm fetches whatever bytes that URL returns and executes any lifecycle scripts contained in them, with no version pin, no hash, and no integrity check. The shipped index.js is a one-line re-export stub (module.exports = require('marker-index-symbol-schema')), so the external host is the entire payload surface and whoever controls artifacts.creditslib.com controls code executed on every installer's machine. The package also carries dependency-confusion markers that aggravate the delivery vector: a vendor-looking scope (@flexmr/survey-client) paired with placeholder metadata (description 'Generated package', author 'Package Registry', repository URL under github.com/example/...), none of which are consistent with a legitimate @flexmr-published client. The artifacts.creditslib.com host is unrelated to any npm registry or to the @flexmr publisher.

Source: ghsa-malware (99e74e2f29511066a66276dd29c8c285d99323ffa8c18eb4deb62c7dcb7fe45a)

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.

Affected packages

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

Versions

All releases from the beginning; no upper bound recorded

No fix recorded for this interval.

5 explicitly affected versions

1.0.0, 1.0.12, 3.0.12, 10.0.12, 2.0.12

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0"
        }
      ],
      "type": "SEMVER"
    }
  ],
  "versions": [
    "1.0.0",
    "1.0.12",
    "3.0.12",
    "10.0.12",
    "2.0.12"
  ]
}

References