MAL-2026-3749 Malicious code in @webapp-next/store (npm)
Malicious package
Published
MAL-2026-3749 is a malicious package: @webapp-next/store (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-3749/ (Markdown: https://insights.sbomify.com/MAL-2026-3749/index.md)
- Package
- @webapp-next/store
- Registry
- npm
What is MAL-2026-3749?
MAL-2026-3749 is a malicious package in @webapp-next/store, published on 14 May 2026.
Official description
package.json declares "preinstall": "node index.js", which runs automatically on npm install. index.js collects os.hostname(), os.platform(), os.arch(), os.homedir(), os.userInfo() (username, uid, gid, shell), OS release/memory/CPU info, process.cwd(), and the output of shell commands
whoami and id, then POSTs the aggregated JSON to https://oia2jeijtfmt053ynp686t5riioac00p.oastify.com/testbydext. The destination is a Burp Suite Collaborator out-of-band interaction subdomain controlled by the attacker. The package has no legitimate functionality — index.js contains only the exfiltration payload, and package.json carries empty author/description fields under a scope (@webapp-next) that resembles a legitimate namespace, consistent with a dependency-confusion lure.What should I do about MAL-2026-3749?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.