Which versions of starship-timeline are malicious?

The following npm versions of starship-timeline are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate starship-timeline if I installed it?

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.

I already installed starship-timeline — how do I know if it already compromised me?

If starship-timeline was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is starship-timeline part of a known attack campaign?

Yes — starship-timeline is associated with the IN-MAL-2026-007539 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find starship-timeline across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for starship-timeline (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging starship-timeline across your stack and pipelines.

Malicious package

starship-timelinenpm

starship-timeline is a confirmed malicious npm package (MAL-2026-6485) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). 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.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

8a4e552337fa70064e0a04644ee5a64378809a85b281eda24707bc9a6eba473f

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for starship-timeline (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging starship-timeline across your stack and pipelines.
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.
Did it already run?
If starship-timeline was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks starship-timeline before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

IN-MAL-2026-007539

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database