Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malicious code in luluking1 (npm)

The npm package luluking1 contained malicious code that downloads and executes arbitrary attacker-controlled payloads at install/import time. The attack vector was obfuscated using char-code arrays to hide the remote URL and shell command from static analysis.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any host installing the malicious package version
Ecosystems
Attack vectors
Affected entities
  • luluking1npm package containing malicious code

The npm package luluking1 was found to contain malicious code in its index.js file. The malicious payload used String.fromCharCode.apply to reconstruct a remote URL and a curl command from numeric char-code arrays at runtime, obfuscating the attack from static inspection.\n\nUpon installation or import, the package reconstructs and executes a shell invocation that downloads an attacker-controlled payload to disk and runs it with the privileges of the installing user. This grants arbitrary code execution on any host that installs the compromised package.\n\nThe use of char-code obfuscation to hide the destination URL and download-and-run command is inconsistent with legitimate installers or SDKs, which typically reference URLs in plain form. This obfuscation technique is a strong indicator of malicious intent.\n\nThe malicious package was identified by Amazon Inspector and credited to the OpenSSF malicious-packages project.

Indicators of compromise

Packages
  • luluking1

Remediation

  • Remove the luluking1 package from all affected systems immediately
  • Audit systems that installed luluking1 for signs of compromise or unauthorized activity
  • Review and revoke any credentials or access tokens that may have been exposed on affected machines
  • Update npm dependencies to remove luluking1 from package-lock.json and package.json
  • Monitor for any suspicious network connections or processes that may have been installed by the malicious payload

Sources

  1. GitHub Advisory GHSA-g5w9-xgvp-xxvh · GitHub Advisory Database

Cite this entry

"Malicious code in luluking1 (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 19, 2026; last updated August 19, 2026. https://supplychainattack.org/incident/malicious-code-in-luluking1-npm-1xv3lc

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. containedcritical

    Malicious code in 3-buildsight-web (npm)

    The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.

    npmCompromised package
  2. resolvedcritical

    Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)

    Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.

    npmDependency confusionCompromised package
  3. resolvedcritical

    Malicious code in create-coin (npm)

    create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.

    npmCompromised packageTyposquatting
  4. resolvedcritical

    Malicious code in @syncraft-labs/vue (npm)

    The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.

    npmCompromised package