Malicious code in luluking3 (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-12399
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (9a95cec14b778c5a61008305c1a4ee8155f777dbe02b6ae5cff25748584105ee) 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.
- Source published
- 5 Aug 2026 13:02:19 UTC
- Source modified
- 5 Aug 2026 13:35:36 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.