Malicious code in tset_racie (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-14550
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (73385958282f9bf88c54065467759596364447d221f34f4c349adb1a849c4871) [email protected] ships a single 45KB obfuscator.io-style payload as its main entry (index.js). The file consists of a 551-entry RC4-encrypted string array, a base64+RC4 decoder, anti-debug self-defense that regex-tests function toString output to detect beautifiers/debuggers, and Function-constructor invocations that build a code string from concatenated decoded entries and immediately invoke it (e.g., `const d=a[...](Function, a[...](a[...](a[...DIBMW...], a[...BHoLQ...]), ');'));H=a[...WEBmW...](d);` followed by `WEBmW: function(H){return H();}`). Anyone who `require()`s this package immediately executes arbitrary code defined by the encrypted strings. The package metadata reinforces malicious intent: gibberish name (`tset_racie`), gibberish author (`ptchli_knldg`), empty description, no repository, no homepage, no dependencies, and no declared purpose — the disposable-publish shape typical of short-lived malicious uploads. The combination of a sole-file eval shell + runtime-assembled Function constructor + anti-debug guards + opaque metadata constitutes embedded malicious code; the encrypted payload's exact target (exfiltration, credential theft, dropper) cannot be statically resolved but the structural shape is unambiguous. ## Source: ghsa-malware (ac46abe681ed7c172e7ca83e577ebe98c1bfd74692b493b07b165a6ed8b6bcd3) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
- Source published
- 26 Aug 2026 22:09:18 UTC
- Source modified
- 31 Aug 2026 18:31:27 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.