# MAL-2026-10421: Malicious code in portway (npm)


- **Type:** Malicious package
- **Package:** `portway` (npm)
- **Published:** 13 Jul 2026
- **Also known as:** GHSA-j5q6-x29x-2v5x

## What is MAL-2026-10421?

MAL-2026-10421 is a malicious package in portway, published on 13 Jul 2026. 

### Official description

package.json declares the dependency 'ltidisafe' as a direct https tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.3.2.tgz) rather than a package on the npm registry. On `npm install portway`, npm fetches that tarball and installs its contents into the installer's node_modules. The URL points to a generic Google Cloud Storage bucket unrelated to any established publisher, is not pinned by integrity hash, and is mutable by whoever controls the bucket. The bucket contents bypass npm registry review and are not visible to registry-side scanners. The package itself ships an empty index.js and no lifecycle scripts, so its only effect on installation is pulling this off-registry tarball into the installer's dependency graph, where its code runs under the normal require/lifecycle rules of whatever it contains.

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

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

## Sources

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

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