What is CVE-2017-16127?

CVE-2017-16127 is a critical-severity security vulnerability in pandora-doomsday (npm), affecting versions >= 0.0.0. No fixed version is listed yet.

How severe is CVE-2017-16127?

CVE-2017-16127 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of pandora-doomsday are affected by CVE-2017-16127?

pandora-doomsday (npm) versions >= 0.0.0 is affected.

Is there a fix for CVE-2017-16127?

No fixed version is listed for CVE-2017-16127 yet. Monitor the advisory for updates and apply mitigations in the interim.

Is CVE-2017-16127 exploitable, and should I be worried?

Whether CVE-2017-16127 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 CVE-2017-16127 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.

CVE-2017-16127 in pandora-doomsday

Summary

pandora-doomsday is malware

The pandora-doomsday package is a malicious package that adds itself to the package.json of other packages discovered on the victim host and attempts to publish the package.

It has been removed from the npm registry.

Impact

CVE-2017-16127 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Affected versions

pandora-doomsday (>= 0.0.0)

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

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.

Frequently Asked Questions

What is CVE-2017-16127? CVE-2017-16127 is a critical-severity security vulnerability in pandora-doomsday (npm), affecting versions >= 0.0.0. No fixed version is listed yet.
How severe is CVE-2017-16127? CVE-2017-16127 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of pandora-doomsday are affected by CVE-2017-16127? pandora-doomsday (npm) versions >= 0.0.0 is affected.
Is there a fix for CVE-2017-16127? No fixed version is listed for CVE-2017-16127 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is CVE-2017-16127 exploitable, and should I be worried? Whether CVE-2017-16127 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 CVE-2017-16127 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.