MAL-2026-17663 Malicious code in mfasolver (npm)
Malicious package
Published
MAL-2026-17663 is a malicious package: mfasolver (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-17663/ (Markdown: https://insights.sbomify.com/MAL-2026-17663/index.md)
- Package
- mfasolver
- Registry
- npm
What is MAL-2026-17663?
MAL-2026-17663 is a malicious package in mfasolver, published on 8 Oct 2026.
Official description
package.json at line 41 declares the only runtime dependency
node-net-pool as https://github.com/trktgq0wbre1/node-net-pool/archive/refs/heads/main.tar.gz — an off-registry HTTP source pointing at the mutable main branch of a GitHub account unrelated to the mfasolver publisher, with no commit pin and no integrity hash. npm install mfasolver fetches whatever bytes that URL returns at install time and runs any lifecycle scripts contained in the fetched archive. The dependency is additionally force-loaded on require: lib/cache.js top-level calls module['require']('node-net-pool') inside a try/catch, so importing mfasolver also executes the attacker-controllable code. Separately, index.js opens TLS connections to discord.com with rejectUnauthorized: false, disabling certificate validation on the package's own Discord traffic.What should I do about MAL-2026-17663?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.