Which versions of luluking2 are malicious?

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

How do I remediate luluking2 if I installed it?

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

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

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

Malicious package

luluking2npm

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

MAL-2026-12398

Immediate action

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

npm uninstall luluking2

What this malware does

On npm install, the package's postinstall hook runs index.js, which reconstructs a URL from a char-code array (String.fromCharCode.apply on a numeric literal array with _0x-prefixed identifiers) resolving to https://aone-kit.oss-cn-beijing.aliyuncs.com/plugins/crypto.js. It shells out via execSync to curl -sL -o ".cache" "<url>", then require()s the downloaded file and deletes it. The destination URL, the filename, and the curl command string are all obfuscated via char-code reconstruction to hide the network destination from source inspection. The remote content is attacker-mutable (an Aliyun OSS bucket) and is executed inside the installing Node process on every install. Package metadata is placeholder-level with no legitimate declared purpose that would justify fetching and executing remote code at install time.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

495a71c4dcddec545026181c7faeef59cf4c79b4816a148fb88c59c5465e8c97

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 luluking2 (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 luluking2 across your stack and pipelines.
If you installed it — respond
luluking2 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 luluking2 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 luluking2 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. luluking2 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-014855

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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