# MAL-2026-10556: Malicious code in @cw-ui/asio-neon-themes (npm)


- **Type:** Malicious package
- **Package:** `@cw-ui/asio-neon-themes` (npm)
- **Published:** 14 Jul 2026
- **Also known as:** GHSA-4966-56x6-595h

## What is MAL-2026-10556?

MAL-2026-10556 is a malicious package in @cw-ui/asio-neon-themes, published on 14 Jul 2026. 

### Official description

On `npm install`, postinstall.js reads `os.hostname()` and embeds it as a query parameter in a plain-HTTP GET to a bare IPv4 address (http://37.60.255.218/skybackground.png?display=<hostname>). This transmits the installer's host identifier to attacker-controlled infrastructure under the cover of an 'image download.' The package metadata, README, and code disagree three ways: package.json declares scope `@cw-ui/asio-neon-themes` ('themes'), README claims 'Simple Text Utils' with capitalize/reverse/wordCount, and the actual shipped code is an image-fetcher beacon. The author field is the placeholder 'Your Name'. The fetch follows arbitrary 301/302 redirects and writes the response bytes to `downloaded-image.jpg` inside the package directory with no integrity check, enabling staged-payload delivery — the endpoint can return any bytes, and the redirect handler accepts any destination.

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

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-10556 is a malicious package: @cw-ui/asio-neon-themes (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-10556/ (Markdown: https://insights.sbomify.com/MAL-2026-10556/index.md)
```

## Sources

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

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