nodecaffe is malware

published 2018-06-07 8y ago modified 2026-06-17 4mo ago also GHSA-2wpq-vvw6-67wr , EUVD-2018-0356

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

nodecaffe was a malicious module published with the intent to hijack environment variables. It has been unpublished by npm.

Is CVE-2017-16070 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.16% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected packages

ecosystem	package	affected	fixed in
npm	nodecaffe	>=0.0.0	no fix listed

Affected products

HackerOne nodecaffe node module

Classification

Weakness

CWE-506 Embedded Malicious Code
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-433 Unparsed Raw Web Content Delivery

References

nodesecurity.io /advisories/509
third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2017-16070
advisory
npmjs.com /advisories/509
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.