Which versions of device-mqtt are affected by GHSA-563H-697M-J7X5?

device-mqtt (npm) versions = 1.0.11 is affected.

Is there a fix for GHSA-563H-697M-J7X5?

No fixed version is listed for GHSA-563H-697M-J7X5 yet. Monitor the advisory for updates and apply mitigations in the interim.

Is GHSA-563H-697M-J7X5 exploitable, and should I be worried?

Whether GHSA-563H-697M-J7X5 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-563H-697M-J7X5 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-563H-697M-J7X5 in device-mqtt

GHSA-563H-697M-J7X5

GHSA-563H-697M-J7X5 is a critical-severity security vulnerability in device-mqtt (npm), affecting versions = 1.0.11. No fixed version is listed yet.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Malicious Package in device-mqtt

Version 1.0.11 of device-mqtt contained malicious code. The code when executed in the browser would enumerate password, cvc, cardnumber fields from forms and send the extracted values to https://js-metrics.com/minjs.php?pl=

Impact

Affected versions

device-mqtt (= 1.0.11)

Security releases

Not available

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Remove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.

Users may consider downgrading to version 1.0.10

Frequently Asked Questions

What is GHSA-563H-697M-J7X5? GHSA-563H-697M-J7X5 is a critical-severity security vulnerability in device-mqtt (npm), affecting versions = 1.0.11. No fixed version is listed yet.
Which versions of device-mqtt are affected by GHSA-563H-697M-J7X5? device-mqtt (npm) versions = 1.0.11 is affected.
Is there a fix for GHSA-563H-697M-J7X5? No fixed version is listed for GHSA-563H-697M-J7X5 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is GHSA-563H-697M-J7X5 exploitable, and should I be worried? Whether GHSA-563H-697M-J7X5 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-563H-697M-J7X5 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.