Which versions of luludawang-kit are malicious?

The following npm versions of luludawang-kit are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate luludawang-kit if I installed it?

luludawang-kit carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.

I already installed luludawang-kit — how do I know if it already compromised me?

If luludawang-kit was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is luludawang-kit part of a known attack campaign?

Yes — luludawang-kit is associated with the IN-MAL-2026-008162, GHSA-vgv8-886r-fvp5 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find luludawang-kit across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for luludawang-kit (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging luludawang-kit across your stack and pipelines.

Malicious package

luludawang-kitnpm

luludawang-kit is a confirmed malicious npm package (MAL-2026-6999) that runs destructive / sabotage code (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in luludawang-kit (npm)

MAL-2026-6999

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall luludawang-kit

What this malware does

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.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ae96a2ee83d724de0e046dbf9e4749e9fd0d5c56fc16f2f28050512080f30628

10e1e712f524e1a88856d4257c90161a701d0469c71cfcdaef0f2bb3994f50bc

Detection & response playbook

Destructive / sabotage

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for luludawang-kit (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging luludawang-kit across your stack and pipelines.
If you installed it — respond
luludawang-kit carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.
Did it already run?
If luludawang-kit was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks luludawang-kit before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. luludawang-kit on npm has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-008162GHSA-vgv8-886r-fvp5

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks luludawang-kit-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database