NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

starship-timelinenpm

Advisory published Updated

starship-timeline is a confirmed malicious npm package (MAL-2026-6485) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in starship-timeline (npm)

MAL-2026-6485
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall starship-timeline

What this malware does

[email protected] 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.

Malicious versions

2 flagged
1.0.11.0.2

Indicators of compromise (SHA-256)

8a4e552337fa70064e0a04644ee5a64378809a85b281eda24707bc9a6eba473f
afc0d28ef1270eb9cb4a35bb75e9a2e5c9e4a8f36fcd25e4979a2d475aa6211b
805d7a3d88b76fd4aa41eae11601b9610d419a3073f9e32ad544279e20587afa

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for starship-timeline (2 malicious versions).

  2. If you installed it — respond

    starship-timeline is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If starship-timeline was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. starship-timeline on npm has been identified as a malicious package (versions 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007539GHSA-7c79-95c2-vgwmIN-MAL-2026-019799

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks starship-timeline-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

starship-timeline (npm) malicious package — MAL-2026-6485 | O3 Security