# MAL-2026-6485: Malicious code in starship-timeline (npm)


- **Type:** Malicious package
- **Package:** `starship-timeline` (npm)
- **Published:** 25 Jun 2026
- **Also known as:** GHSA-7c79-95c2-vgwm

## What is MAL-2026-6485?

MAL-2026-6485 is a malicious package in starship-timeline, published on 25 Jun 2026. 

### Official description

starship-timeline@1.0.1 ships no real functionality. Its package.json declares a preinstall hook (`"preinstall": "node index.js"`) that runs automatically on `npm install`. index.js collects hostname, username, home directory, DNS servers, package metadata, and the contents of `/etc/passwd` and `/etc/hosts`, then POSTs the bundle over HTTPS to a hardcoded Burp Collaborator (`*.oastify.com`) subdomain (`5tziqozihbss8jg955ez91bycpij69uy.oastify.com`). The package has empty author and description fields, a single published version, and no other code paths — the exfiltration beacon is its only purpose, matching the standard dependency-confusion / OOB-beacon pattern. Whether deployed as research or as a live attack, installing the package leaks identifying host data and sensitive system files to an attacker-controlled out-of-band endpoint.

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

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

## Sources

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

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