yandex-geobase (npm) · Malicious Code
Affects yandex-geobaseSource GCVE Database
Malicious package : remove yandex-geobase and rotate any secrets on hosts that installed it.
Data as of 21 Aug 2026, 16:28 UTC
Malicious package
Published to npm · OSV MAL-2026-6574
What to do
Remove yandex-geobase from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmyandex-geobase | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The yandex-geobase npm package versions 2.1.0, 2.1.2, 2.2.0, 2.9.0, and 3.9.0 contain malicious code that executes a postinstall script. This script sends an HTTP GET request to a hardcoded bare IP address on a non-standard port, leaking package and environment information to an external host. The package is described as a dependency confusion test placeholder, but its behavior can compromise build environments and potentially the host system. Removal of the package is recommended, but full system compromise is possible, requiring secret and key rotation.
References
- npmjs.com/package/yandex-geobase/v/2.9.0 (opens in a new tab)
- npmjs.com/package/yandex-geobase/v/2.1.2 (opens in a new tab)
- npmjs.com/package/yandex-geobase/v/3.9.0 (opens in a new tab)
- npmjs.com/package/yandex-geobase/v/2.1.0 (opens in a new tab)
- npmjs.com/package/yandex-geobase/v/2.2.0 (opens in a new tab)
- npmjs.com/package/yandex-geobase/v/2.1.1 (opens in a new tab)
- github.com/advisories/GHSA-86q5-cfp8-j54g (opens in a new tab)