Malicious code in luluking (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-12397
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (3b88d4d8ec638e21c3b126dc9416ed8e2f3781bb1cc1d8ebe5a6579d698c6082) 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.
- Source published
- 5 Aug 2026 13:08:01 UTC
- Source modified
- 5 Aug 2026 13:35:35 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.