Which versions of luluking1 are malicious?

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

How do I remediate luluking1 if I installed it?

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

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

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

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

Malicious package

luluking1npm

Advisory published Aug 19, 2026Updated Aug 19, 2026

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

MAL-2026-14250

Immediate action

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

npm uninstall luluking1

What this malware does

index.js stores a remote URL and a curl -sL -o command as numeric char-code arrays and reconstructs them at runtime with String.fromCharCode.apply, then fetches and executes the retrieved content at install/import time. Hiding the destination and the download-and-run command behind char-code obfuscation is inconsistent with any legitimate installer or SDK, which references URLs in plain form. The reconstructed shell invocation downloads an attacker-controlled payload to disk and runs it on the installer's machine, giving whoever published the package arbitrary code execution on any host that installs it.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fdd9bc7980d937f728e8beb92d789d75a1dc02fd56bdfb545cd33f255952bcf4

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for luluking1 (version 0.0.1).
If you installed it — respond
Remove luluking1 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 luluking1 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. luluking1 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-018361

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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