# MAL-2026-10283: Malicious code in another-poc-by-tipsen (npm)


- **Type:** Malicious package
- **Package:** `another-poc-by-tipsen` (npm)
- **Published:** 13 Jul 2026
- **Also known as:** GHSA-r459-5pr6-64j7

## What is MAL-2026-10283?

MAL-2026-10283 is a malicious package in another-poc-by-tipsen, published on 13 Jul 2026. 

### Official description

package.json declares a dependency `safe-chain-test` sourced from a tarball URL on an anonymous Cloudflare tunnel host (`periods-parcel-pittsburgh-upgrading.trycloudflare.com`) rather than the npm registry or a pinned git SHA. On `npm install`, npm fetches and installs whatever bytes that ephemeral, publisher-controlled host serves at the moment of resolution, bypassing registry scanning and integrity pinning. The tunnel operator can change the served bytes at any time, so the installer's dependency graph resolves to arbitrary, unverifiable code executed with the transitive package's install-time and require-time privileges. The package itself is otherwise empty (only package.json and README.md; declared `main` index.js is absent), so the sole effect of installing it is to pull in the tunnel-hosted tarball.

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

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

## Sources

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

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