If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (ce04d25dced1e4c2398d7d91568783b983f326444098ecff8ddf7c29468d752c)
kmf-i18n@100.100.100 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.