pandora-doomsday is malware

published 2018-06-07 8y ago modified 2026-06-17 4mo ago also GHSA-428f-mh7w-6w2x , EUVD-2020-0716

cvss: 9.8; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.4%; EPSS 1.4% chance of exploitation in 30 days, percentile 73%
public exploits: 0; none known

The module pandora-doomsday infects other modules. It's since been unpublished from the registry.

Is CVE-2017-16127 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.43% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	9.8	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	10.0	AV:N/AC:L/Au:N/C:C/I:C/A:C
GitHub	3.0	9.8	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
npm	pandora-doomsday	>=0.0.0	no fix listed

Affected products

HackerOne pandora-doomsday node module

Classification

Weakness

CWE-509 Replicating Malicious Code (Virus or Worm)
CWE-276 Incorrect Default Permissions

References

nodesecurity.io /advisories/482
third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2017-16127
advisory
npmjs.com /advisories/482
web

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.