# MAL-2026-6068: Malicious code in swift-parse-stream (npm)


- **Type:** Malicious package
- **Package:** `swift-parse-stream` (npm)
- **Published:** 17 Jun 2026
- **Also known as:** GHSA-qcr2-hwcg-gf9g

## What is MAL-2026-6068?

MAL-2026-6068 is a malicious package in swift-parse-stream, published on 17 Jun 2026. 

### Official description

swift-parse-stream advertises itself as an SVG sanitizer/minifier but ships an undocumented `getPlugin` export in index.js that, when invoked, performs an HTTP GET against https://www.jsonkeeper.com/b/3P9BF (an anonymous user-paste host) and runs `eval(parsed.model)` on the returned JSON's `model` field. The destination is attacker-controlled and mutable: whoever controls the paste can change the executed JavaScript at any time without republishing the package. The README does not mention this code path. Any caller — typically a second compromised package chaining into this one — that reaches `getPlugin()` hands arbitrary remote code execution to the paste's owner, running in the consumer application's process with its full privileges and access to its environment, filesystem, and network.

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

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

## Sources

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

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