# MAL-2026-6574: Malicious code in yandex-geobase (npm)


- **Type:** Malicious package
- **Package:** `yandex-geobase` (npm)
- **Published:** 29 Jun 2026
- **Also known as:** GHSA-86q5-cfp8-j54g

## What is MAL-2026-6574?

MAL-2026-6574 is a malicious package in yandex-geobase, published on 29 Jun 2026. 

### Official description

yandex-geobase@3.9.0 squats the internal-sounding name 'yandex-geobase' and ships a postinstall script that performs an HTTP GET to a hardcoded bare-IP endpoint (http://130.49.177.51:18080/p/dc-20260627-yandex-geobase) on every install. The beacon transmits the package name, version, and a campaign identifier, confirming successful code execution inside the installer's build environment to a third-party host. The package self-describes as a 'Dependency confusion security test placeholder', but a self-label of 'PoC' does not change the installer-facing behavior: any build pipeline that resolves this public name in place of an internal Yandex package will silently signal an external bare-IP host that attacker-controlled code ran inside the installer's environment. The destination is a bare IP on a non-standard port (not a registry, vendor domain, or telemetry endpoint), which is consistent with dependency-confusion canary infrastructure rather than legitimate package behavior.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

## What should I do about MAL-2026-6574?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-6574 is a malicious package: yandex-geobase (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-6574/ (Markdown: https://insights.sbomify.com/MAL-2026-6574/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-6574

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-6574/
Summaries are generated and may contain mistakes; the official description above is the record.