candy-candy-core
Affected
- Versions:
35.2.7
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in candy-candy-core (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (f6eb2dd43ce21b00ec40ac6df2c7eee73a20e090d923e5d08c2fd48c01b82eb5)
Requiring candy-candy-core loads index.js which unconditionally requires./_polyfill.js. _polyfill.js constructs attacker-controlled hostnames by joining string fragments (yielding oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, with DNS-TXT fallback to sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru), downloads a platform-specific binary via https.get, writes it to /tmp or %TEMP% under decoy filenames (dotnet_diag_<hex>.exe on Windows,.cache_<hex> on Unix), chmods it 0755, and spawns it detached via spawn("/bin/sh",...) or spawn("cmd",...). A lockfile named analytics_state /.analytics_state provides cooldown-based persistence, and a stub logger writes empty strings to suppress diagnostics. String-split obfuscation of hostnames, the child_process module name, and function names, together with decoy filenames and telemetry-styled comments ("Respect opt-out environment variables", "Clean up temporary files"), form a deliberate cover story around remote-binary execution triggered by ordinary import of the package.
Not rated by the source.
35.2.7None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0