Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

tset_racienpm

Advisory published Updated

tset_racie is a confirmed malicious npm package (MAL-2026-14550) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tset_racie (npm)

MAL-2026-14550
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall tset_racie

What this malware does

[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.

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.

Malicious versions

4 flagged
1.0.01.0.11.0.21.0.3

Indicators of compromise (SHA-256)

ac46abe681ed7c172e7ca83e577ebe98c1bfd74692b493b07b165a6ed8b6bcd3
73385958282f9bf88c54065467759596364447d221f34f4c349adb1a849c4871
8568dfae4b1862bc86e81f5cff411ef39aa06302cf0b0820c0c470825f8c619d
a55937cff3fedcd0473327b498f2718379087e37a1f84ccef60c5318c2d5c48a
d1b5c54415e9d95716a0823370bbd3d3787fb20d992a90fdcf2c5985536b09c8

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for tset_racie (4 malicious versions).

  2. If you installed it — respond

    tset_racie is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If tset_racie was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. tset_racie on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-7978-5fh2-74q2IN-MAL-2026-018798IN-MAL-2026-018797IN-MAL-2026-019204IN-MAL-2026-019202

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks tset_racie-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

tset_racie (npm) malicious package — MAL-2026-14550 | O3 Security