# MAL-2026-17433: Malicious code in figma-to-apl (npm)


- **Type:** Malicious package
- **Package:** `figma-to-apl` (npm)
- **Published:** 30 Sep 2026

## What is MAL-2026-17433?

MAL-2026-17433 is a malicious package in figma-to-apl, published on 30 Sep 2026. 

### Official description

figma-to-apl 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 figma-to-apl and 9 similar packages within two minutes on 2026-09-30, all with the same setup.js.

figma-to-apl@100.0.0 declares a preinstall script ("node setup.js || true") that runs automatically on npm install. setup.js collects installer-side identifiers — os.hostname(), os.userInfo().username, process.cwd(), process.platform, process.arch, Node version, and the configured npm registry — and POSTs them together with a hardcoded per-package token to https://s85r5k14qk.execute-api.us-east-1.amazonaws.com/prod/hook. The package's advertised functionality is a one-line string-truncation helper, unrelated to the beacon. The version number 100.0.0 combined with a per-package identifying token is characteristic of a dependency-confusion / typosquat reconnaissance probe designed to identify internal build systems that resolve the public package name.

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

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-17433 is a malicious package: figma-to-apl (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-17433/ (Markdown: https://insights.sbomify.com/MAL-2026-17433/index.md)
```

## Sources

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

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