# MAL-2026-10391: Malicious code in tipsen-last (npm)


- **Type:** Malicious package
- **Package:** `tipsen-last` (npm)
- **Published:** 13 Jul 2026
- **Also known as:** GHSA-83fp-39mc-pvp5

## What is MAL-2026-10391?

MAL-2026-10391 is a malicious package in tipsen-last, published on 13 Jul 2026. 

### Official description

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.

## What should I do about MAL-2026-10391?

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

## Sources

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

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