Which versions of luluking are malicious?

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

How do I remediate luluking if I installed it?

luluking 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 luluking — how do I know if it already compromised me?

If luluking was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is luluking part of a known attack campaign?

Yes — luluking is associated with the IN-MAL-2026-014895 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 luluking across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for luluking (version 0.0.1).

Malicious package

lulukingnpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

luluking is a confirmed malicious npm package (MAL-2026-12397) 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 luluking (npm)

MAL-2026-12397

Immediate action

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

npm uninstall luluking

What this malware does

On npm install, the package's postinstall hook runs index.js, which reconstructs a URL and shell command from String.fromCharCode numeric arrays, invokes curl to download a remote script to a local.cache file, require()s it to execute the fetched Node code, then deletes the file. The decoded destination is https://aone-kit.oss-cn-beijing.aliyuncs.com/plugins/crypto.js — a non-publisher endpoint. The charcode-array obfuscation of both the URL and the curl command hides the behavior from casual inspection. Installing the package yields arbitrary code execution on the installer's machine with content the author can change at any time.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3b88d4d8ec638e21c3b126dc9416ed8e2f3781bb1cc1d8ebe5a6579d698c6082

Detection & response playbook

Destructive / sabotage

Find it
Search your lockfiles and build artifacts for luluking (version 0.0.1).
If you installed it — respond
luluking 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 luluking was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. luluking 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-014895

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks luluking-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