Which versions of luluking3 are malicious?

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

How do I remediate luluking3 if I installed it?

Remove luluking3 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed luluking3 — how do I know if it already compromised me?

If luluking3 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 luluking3 part of a known attack campaign?

Yes — luluking3 is associated with the IN-MAL-2026-014858 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 luluking3 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 luluking3 (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 luluking3 across your stack and pipelines.

Malicious package

luluking3npm

luluking3 is a confirmed malicious npm package (MAL-2026-12399) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in luluking3 (npm)

MAL-2026-12399

Immediate action

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

npm uninstall luluking3

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 char-code arrays (obfuscated behind _0x-prefixed variables), invokes curl -sL -o <hidden.cache path> to download https://aone-kit.oss-cn-beijing.aliyuncs.com/plugins/crypto.js, require()s the downloaded file inside the installer's Node process, and then unlinks it. The remote endpoint is a third-party Aliyun OSS bucket whose contents are mutable and controlled by the publisher, so arbitrary attacker-supplied JavaScript executes with the privileges of the user running npm install. Obfuscation of both the URL and the shell command indicates intent to evade static inspection.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9a95cec14b778c5a61008305c1a4ee8155f777dbe02b6ae5cff25748584105ee

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for luluking3 (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 luluking3 across your stack and pipelines.
If you installed it — respond
Remove luluking3 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If luluking3 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 luluking3 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. luluking3 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-014858

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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