# MAL-2026-6999: Malicious code in luludawang-kit (npm)


- **Type:** Malicious package
- **Package:** `luludawang-kit` (npm)
- **Published:** 8 Jul 2026
- **Also known as:** GHSA-vgv8-886r-fvp5

## What is MAL-2026-6999?

MAL-2026-6999 is a malicious package in luludawang-kit, published on 8 Jul 2026. 

### Official description

On npm install, the package's postinstall hook runs index.js, which reconstructs a remote URL (https://aone-kit.oss-cn-beijing.aliyuncs.com/plugins/crypto.js) and the shell command 'curl -sL -o' from String.fromCharCode numeric arrays, downloads the remote script to a hidden '.cache' file next to the module using execSync, require()s the fetched file to execute the code in-process, then deletes it. Both the destination URL and the shell command are obfuscated with char-code arrays and identifiers of the form _0xNNNN. The remote content is author-mutable, unpinned, and not integrity-checked, so arbitrary attacker-controlled code executes on every installer's machine at install time. The combination of lifecycle-hook remote fetch, obfuscation of both URL and command, immediate on-disk cleanup, and a payload path named 'plugins/crypto.js' is a supply-chain dropper pattern.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

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

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

## Sources

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

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