Vulnerability · MAL-2026-17899
Malicious code in @flexmr/survey-conversation (npm)
Published Oct 16, 2026 · catalog updated Oct 16, 2026 · Malicious code in @flexmr/survey-conversation
Open the advisory
Exploitation likelihood is not on this record for MAL-2026-17899. A missing EPSS score is not a low risk. Compare Malicious code in @flexmr/survey-conversation with the linked advisory before you change production.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (Malicious code in @flexmr/survey-conversation).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- EPSS is missing. A missing score is not a low risk.
- Severity
- Unknown—
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- Awaiting synchronization with FIRST
- Remediation
- Not established
- Affected products
- npm @flexmr/survey-conversation
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (20ab57dd6ac5a0eafc23934f6e715064453641bc57a549050f1d2e66a7630374) package.json declares its sole dependency as a bare HTTPS URL ( ) rather than a registry version range. On , 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 is a one-line re-export of that dependency, so runtime behavior is also fully delegated to the externally-hosted bytes. Whoever controls 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 scope with placeholder author/publisher metadata ( , ), consistent with a dependency-confusion lure targeting an internal package name.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- npm @flexmr/survey-conversation1.0.12, 10.0.12, 2.0.12
How to fix MAL-2026-17899
Recommended remediation
No required-action text, fix commit, or clear fixed-version range is stored yet.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
Exploitation likelihood is not on this record for MAL-2026-17899. A missing EPSS score is not a low risk. Compare Malicious code in @flexmr/survey-conversation with the linked advisory before you change production.
Which versions are affected?
Compare what you have installed with 1.0.12, 10.0.12, 2.0.12. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 16, 2026 · OpenSSF OSV / OSV Scanner
Detected
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (20ab57dd6ac5a0eafc23934f6e715064453641bc57a549050f1d2e66a7630374) package.json declares its sole dependency as a bare HTTPS URL ( ) rather than a registry version range. On , npm fetches whatever bytes that host serves and executes any lifecycle scripts inside, with no version pin, no registry integrity check,
Oct 16, 2026 · OpenSSF OSV / OSV Scanner
Updated
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (20ab57dd6ac5a0eafc23934f6e715064453641bc57a549050f1d2e66a7630374) package.json declares its sole dependency as a bare HTTPS URL ( ) rather than a registry version range. On , npm fetches whatever bytes that host serves and executes any lifecycle scripts inside, with no version pin, no registry integrity check,
Sources
- OpenSSF OSV / OSV ScannerPackage advisoryMAL-2026-17899
Malicious code in @flexmr/survey-conversation (npm)
osv.dev
References
Freshness
Last verified in this catalog Oct 16, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.