Malicious code in kmf-i18n (npm)
Collected exploitation and prediction evidence
Risk source coverageCISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.
No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.
osv · MAL-2026-17747
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (ce04d25dced1e4c2398d7d91568783b983f326444098ecff8ddf7c29468d752c) [email protected] is published with the version-number and behavior shape of a dependency-confusion reconnaissance beacon rather than an i18n library. The tarball ships a Linux x64 N-API binary at prebuilds/linux-x64/addon.node with no corresponding source, no binding.gyp, and no build step. package.json declares scripts.postinstall = "node postinstall.js", and postinstall.js require()s that prebuilt.node binary, so the native code is loaded automatically on npm install. The addon opens a raw TCP socket to the hardcoded bare IP 64.181.165.115 on port 80 and sends an HTTP/1.0 POST to /dc with body h=<HOSTNAME>&p=<npm_package_name>&u=<unused>&r=<npm_config_registry>, reading those values from the installer's environment. The exfiltrated npm_config_registry value discloses internal/private npm registry URLs, which is the characteristic signal of dependency-confusion target reconnaissance. The addon exposes no i18n functionality consistent with the package's declared purpose; its only observable behavior is the install-time beacon. The main entry also require()s the same binary, so merely importing the package re-triggers the native load path. ## Source: ossf-package-analysis (c506e33bdce28606141b7d2bbebbae50e97e466ab04664a9cca8fa48a3622ae1) The OpenSSF Package Analysis project identified 'kmf-i18n' @ 100.100.102 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.
- Source published
- 9 Oct 2026 19:10:42 UTC
- Source modified
- 11 Oct 2026 14:30:09 UTC
- Observed here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.