# MAL-2026-6586: Malicious code in yastatic-s3 (npm)


- **Type:** Malicious package
- **Package:** `yastatic-s3` (npm)
- **Published:** 29 Jun 2026
- **Also known as:** GHSA-mj8p-qhh7-gvg4

## What is MAL-2026-6586?

MAL-2026-6586 is a malicious package in yastatic-s3, published on 29 Jun 2026. 

### Official description

Package name mimics Yandex's `yastatic` static-asset namespace. On install, postinstall.js performs an unconditional plain-HTTP GET to a hardcoded bare-IP endpoint http://130.49.177.51:18080/p/dc-20260627-yandex-geobase with query parameters carrying only the package name, version, and a fixed nonce. No environment variables, filesystem contents, credentials, or host identifiers are read or transmitted, and no code is fetched or executed from the remote endpoint. The behavior is a namespace-squatting placeholder with an install-time execution beacon: it confirms to the operator of the bare-IP endpoint that a target environment misresolved the public name into a private dependency tree. Installing this package does not exfiltrate installer data or execute attacker-controlled code, but it does reveal internal install activity to a third-party endpoint and occupies a namespace that resembles a well-known vendor's.

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-6586?

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-6586 is a malicious package: yastatic-s3 (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-6586/ (Markdown: https://insights.sbomify.com/MAL-2026-6586/index.md)
```

## Sources

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

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