@united-airlines-org/atmos-design-systemnpm
@united-airlines-org/atmos-design-system is a confirmed malicious npm package (MAL-2026-13435) that steals credentials and exfiltrates sensitive data (malicious versions 40.0.0, 41.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @united-airlines-org/atmos-design-system (npm)
What this malware does
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/[email protected] 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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @united-airlines-org/atmos-design-system (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @united-airlines-org/atmos-design-system across your stack and pipelines.
If you installed it — respond
@united-airlines-org/atmos-design-system is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @united-airlines-org/atmos-design-system was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @united-airlines-org/atmos-design-system before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- SafeDep · finder
Detect & block this
O3 blocks @united-airlines-org/atmos-design-system-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.