# MAL-2026-13435: Malicious code in @united-airlines-org/atmos-design-system (npm)


- **Type:** Malicious package
- **Package:** `@united-airlines-org/atmos-design-system` (npm)
- **Published:** 6 Aug 2026

## What is MAL-2026-13435?

MAL-2026-13435 is a malicious package in @united-airlines-org/atmos-design-system, published on 6 Aug 2026. 

### Official description

The package @united-airlines-org/atmos-design-system contains a malicious `preinstall` script in its package.json that runs automatically during installation. The script executes `curl` to send the machine's hostname, obtained via `uname -n` and base64-encoded, to the attacker-controlled endpoint `https://bxss.boll-sec.de/hostname_<base64-hostname>`. This exfiltrates host reconnaissance data to a remote server. All versions of the package are malicious.

Package @united-airlines-org/atmos-design-system@41.0.0 ships no library code — only a package.json whose `preinstall` script runs `/usr/bin/curl` to https://bxss.boll-sec.de/callb with base64-encoded values of `uname -n`, `ls` of the current directory, and `whoami` as query parameters. This fires automatically on `npm install`, sending the installer's hostname, working-directory listing, and username to an external, non-first-party host. The scope name resembles an internal United Airlines organization and the package contains no functional code beyond the beacon, matching the dependency-confusion pattern in which resolution of an internal package name pulls in an attacker-published public artifact.

## What should I do about MAL-2026-13435?

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-13435 is a malicious package: @united-airlines-org/atmos-design-system (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-13435/ (Markdown: https://insights.sbomify.com/MAL-2026-13435/index.md)
```

## Sources

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

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