# MAL-2026-6707: Malicious code in svgson-lite (npm)


- **Type:** Malicious package
- **Package:** `svgson-lite` (npm)
- **Published:** 1 Jul 2026
- **Also known as:** GHSA-g7rx-jhhj-8whr

## What is MAL-2026-6707?

MAL-2026-6707 is a malicious package in svgson-lite, published on 1 Jul 2026. 

### Official description

index.js exports an undocumented getPlugin() function which, when invoked, performs an HTTP GET to https://shorturl.at/147uq, JSON-parses the response body, and passes the response's `model` field directly to eval(). The URL is a mutable shortener redirect controlled by the package author and can be repointed to any JavaScript payload at any time, giving the author arbitrary code execution in the process of any consumer that calls getPlugin()(). The package's stated purpose is an SVG helper: package.json describes it as 'Tiny zero-dependency SVG helper for Node.js' and declares no dependencies, yet index.js requires the 'request' library and implements the fetch+eval path. The network+eval behavior is unrelated to SVG processing and is not mentioned in the README, keywords, or exports documentation. The mismatch between advertised purpose and shipped behavior, combined with the shortener-cloaked destination, is deliberate concealment of a backdoor surface.

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

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

## Sources

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

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