# MAL-2026-5456: Malicious code in via-city-tools-m-particle (npm)


- **Type:** Malicious package
- **Package:** `via-city-tools-m-particle` (npm)
- **Published:** 9 Jun 2026
- **Also known as:** GHSA-6wg4-xxqc-hw9h

## What is MAL-2026-5456?

MAL-2026-5456 is a malicious package in via-city-tools-m-particle, published on 9 Jun 2026. 

### Official description

The package exports an empty object (`module.exports = {}`) and has no functionality of its own. Its only substantive effect is to declare a dependency on `ltidisafe` pinned to the off-registry tarball URL `https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.7.6.tgz`. Installing this package causes npm to fetch and install that arbitrary tarball — hosted in a generic Google Cloud Storage bucket with no registry integrity guarantees and no publisher binding — and any lifecycle scripts (`preinstall`/`install`/`postinstall`) inside it run automatically on the installer's machine. The package metadata is hollow (empty `description`, empty `author`, no `repository`), and the unscoped name `via-city-tools-m-particle` resembles legitimate scoped tooling, consistent with a dependency-confusion lure whose only purpose is to smuggle the off-registry tarball into target build environments.

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

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-5456 is a malicious package: via-city-tools-m-particle (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-5456/ (Markdown: https://insights.sbomify.com/MAL-2026-5456/index.md)
```

## Sources

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

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