# MAL-2026-17435: Malicious code in niksinnkatalapp (npm)


- **Type:** Malicious package
- **Package:** `niksinnkatalapp` (npm)
- **Published:** 30 Sep 2026

## What is MAL-2026-17435?

MAL-2026-17435 is a malicious package in niksinnkatalapp, published on 30 Sep 2026. 

### Official description

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

The package declares a preinstall hook that runs setup.js on `npm install`. setup.js collects host identifiers (os.hostname(), os.userInfo().username, process.cwd(), platform, arch, node version, and the configured npm registry) and POSTs them as JSON, together with a hardcoded correlation token, to https://s85r5k14qk.execute-api.us-east-1.amazonaws.com/prod/hook. The advertised purpose is a trivial celsius-to-fahrenheit conversion, which does not require telemetry or network activity. The package name and 100.0.0 version pin are consistent with a dependency-confusion lure intended to win resolution against an internal package name and beacon out from build environments that install it.

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

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

## Sources

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

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