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


- **Type:** Malicious package
- **Package:** `tipsen-last-pls` (npm)
- **Published:** 13 Jul 2026
- **Also known as:** GHSA-r7j6-rpc2-h6xh

## What is MAL-2026-10392?

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

### Official description

package.json declares a dependency `safe-chain-test` whose version specifier is a direct HTTPS tarball URL on an anonymous Cloudflare ephemeral tunnel: `https://harris-encourage-westminster-political.trycloudflare.com/safe-chain-test-1.0.0.tgz`. On `npm install`, npm fetches and installs the tarball from this non-registry, mutable, non-publisher-owned host and runs any lifecycle scripts inside it. The tarball is not pinned by integrity hash, is not hosted on the npm registry or a publisher-owned domain, and its contents are entirely controlled by whoever operates the tunnel — enabling arbitrary code execution on the installer's machine at install time. The manifest self-describes as 'Safe Chain transitive tarball scanning reproduction' and ships no code of its own (declared `main: index.js` is absent), so the package's sole effect on install is to resolve and execute the tunnel-hosted dependency.

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

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

## Sources

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

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