# MAL-2026-13467: Malicious code in wos-library-ui (npm)


- **Type:** Malicious package
- **Package:** `wos-library-ui` (npm)
- **Published:** 6 Aug 2026
- **Also known as:** GHSA-j5rq-m53m-6xfx, GHSA-wh36-rj36-m3ff

## What is MAL-2026-13467?

MAL-2026-13467 is a malicious package in wos-library-ui, published on 6 Aug 2026. 

### Official description

wos-library-ui@99.0.0 declares scripts.preinstall = 'node poc.js', which auto-runs on npm install. poc.js reads os.hostname(), os.userInfo().username, and process.cwd() and transmits them to the hardcoded Interactsh subdomain csytkgaubytabdgcvgljmgf8o1uj876pg.oast.fun via both a DNS A-record lookup (encoding host/user in the subdomain) and an http.request POST. The package name and inflated 99.0.0 version match the classic dependency-confusion shape targeting an internal 'wos-library-ui' package (self-described as an Inditex WOS PoC): any resolver that prefers the public npm registry will pull this artifact instead of the internal one and execute the beacon, disclosing internal host identifiers and build-path details to a third-party out-of-band collector. Self-labeling as a bug-bounty PoC does not alter the installer-side effect: unconsented install-time exfiltration of installer identity from a namesquatted package on the public registry.

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

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-13467 is a malicious package: wos-library-ui (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-13467/ (Markdown: https://insights.sbomify.com/MAL-2026-13467/index.md)
```

## Sources

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

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