# MAL-2026-17427: Malicious code in ai-workshop-maa15-radio (npm)


- **Type:** Malicious package
- **Package:** `ai-workshop-maa15-radio` (npm)
- **Published:** 30 Sep 2026

## What is MAL-2026-17427?

MAL-2026-17427 is a malicious package in ai-workshop-maa15-radio, published on 30 Sep 2026. 

### Official description

ai-workshop-maa15-radio is a dependency-confusion package: it takes a name that looks like an internal project, uses an inflated version (100.0.0) so it outranks private-registry versions, and runs `node setup.js || true` as a preinstall script on npm install. setup.js sends the hostname, username, working directory, OS, architecture, Node.js version and configured npm registry, with a per-package tracking token, in an HTTPS POST to `https://s85r5k14qk.execute-api.us-east-1.amazonaws.com/prod/hook`. The npm account amel10 published ai-workshop-maa15-radio and 9 similar packages within two minutes on 2026-09-30, all with the same setup.js.

Package advertises itself as a trivial string helper (reverseWords) but its declared preinstall script (node setup.js) opens an HTTPS POST to a hardcoded endpoint at s85r5k14qk.execute-api.us-east-1.amazonaws.com/prod/hook on every npm install. The request body contains os.hostname(), os.userInfo().username, process.cwd(), os.platform(), os.arch(), process.version, and npm_config_registry, along with a hardcoded per-package tracking token. The version number (100.0.0) and the collection of npm_config_registry are consistent with a dependency-confusion reconnaissance beacon targeting internal package resolution. Installer host and user identifiers are transmitted to an attacker-controlled endpoint without consent, fired automatically at install time.

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

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-17427 is a malicious package: ai-workshop-maa15-radio (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-17427/ (Markdown: https://insights.sbomify.com/MAL-2026-17427/index.md)
```

## Sources

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

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