niksinnkatalappnpm
Advisory published Updated
niksinnkatalapp is a confirmed malicious npm package (MAL-2026-17435) that steals credentials and exfiltrates sensitive data (malicious version 100.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in niksinnkatalapp (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for niksinnkatalapp (version 100.0.0).
If you installed it — respond
niksinnkatalapp is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If niksinnkatalapp was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- InvisiRisk, Inc. · finder
Detect & block this
O3 blocks niksinnkatalapp-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.