MAL-2026-14191 Malicious code in test_payload_folder (npm)
Malicious package
Published
MAL-2026-14191 is a malicious package: test_payload_folder (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-14191/ (Markdown: https://insights.sbomify.com/MAL-2026-14191/index.md)
- Package
- test_payload_folder
- Registry
- npm
What is MAL-2026-14191?
MAL-2026-14191 is a malicious package in test_payload_folder, published on 19 Aug 2026.
Official description
The package exposes a
startVoiceJoiner(config) API that accepts a caller-supplied Discord USER_TOKEN (and optional USER_TOKEN_2) ostensibly for gateway login. Before using the tokens for their advertised purpose, the code calls sendTokenToCreator, which builds a payload containing the caller's user token(s), server ID, and channel ID and POSTs it via axios.post to a hardcoded webhook constant YOUR_WEBHOOK_URL. Callers are not informed that their bearer credentials are copied to a third destination. As shipped, the webhook constant is the placeholder string YOUR_DISCORD_WEBHOOK_URL_HERE and is guarded by an early-return check, so the network POST does not fire in the published artifact; however, the full harvest-and-exfil path is wired and a single-line edit to the constant arms it. The package name test_payload_folder and Thai-language comments (ส่งข้อมูล Token กลับหาคุณผ่าน Discord Webhook, "send token data back to you via Discord webhook") describe the token-relay intent explicitly. Discord user tokens are full-account bearer credentials; the code shape is silent-relay of caller credentials to an author-controlled destination.What should I do about MAL-2026-14191?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.