Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

tipsen-lastnpm

tipsen-last is a confirmed malicious npm package (MAL-2026-10391) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tipsen-last (npm)

MAL-2026-10391
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall tipsen-last

What this malware does

package.json declares its only runtime dependency ("safe-chain-test") as a direct tarball URL on hoped-twice-evaluation-site.trycloudflare.com — an ephemeral, anonymous Cloudflare tunnel host with no publisher identity, no version pinning, and no hash or signature verification. On npm install, npm fetches whatever bytes the tunnel operator is serving at that moment and installs the result into the dependency tree; the transitive tarball can declare its own preinstall/install/postinstall lifecycle scripts, which npm will execute against the installer's machine. The tunnel operator can swap the served content at will, so even a benign snapshot today provides no assurance about tomorrow. The package itself ships no code (the declared main index.js is absent from the tarball) — its entire install-time effect is to pull attacker-mutable code into the installer's environment.

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

1 flagged
1.0.0

Indicators of compromise (SHA-256)

afc3164ae4341c343f4489e9e31f8031f2d3b2f1646f0c0e57b0471d6752d3e8
d8dda277dd82e1c50906cff18341bb76485eed33ba42d39b228c447514e4081f

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove tipsen-last from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If tipsen-last 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.

  4. How O3 protects you

    O3 blocks tipsen-last 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. tipsen-last on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-83fp-39mc-pvp5IN-MAL-2026-009859

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks tipsen-last-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

tipsen-last (npm) malicious package — MAL-2026-10391 | O3 Security