# MAL-2026-18115: Malicious code in tellyo-colours (npm)


- **Type:** Malicious package
- **Package:** `tellyo-colours` (npm)
- **Published:** 20 Oct 2026
- **Also known as:** GHSA-4q6x-w65x-677r

## What is MAL-2026-18115?

MAL-2026-18115 is a malicious package in tellyo-colours, published on 20 Oct 2026. 

### Official description

tellyo-colours@21.3.1 declares a runtime dependency on `abbishal-poc-as-dependency` with the wildcard version `"*"` in package.json, despite the README stating the package ships no code and no install scripts. On `npm install`, resolution of the wildcard range fetches whichever version the controller of that dependency name currently publishes and executes any lifecycle scripts (preinstall/install/postinstall) shipped in that transitive package. The shipped SCSS contains the canary string `--tostpro-canary: "test by abbishal"`, matching the dependency's author prefix and indicating the two artifacts are coordinated as a dependency-confusion proof-of-concept. The inert nature of the SCSS content and the absence of lifecycle scripts in this package do not mitigate the exposure — the manifest itself is sufficient to pull and run arbitrary code from the dependency on install.

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

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-18115 is a malicious package: tellyo-colours (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-18115/ (Markdown: https://insights.sbomify.com/MAL-2026-18115/index.md)
```

## Sources

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

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