@ceeferenderer/itg-renderer-sdknpm
Advisory published Updated
@ceeferenderer/itg-renderer-sdk is a confirmed malicious npm package (MAL-2026-2407) that steals credentials and exfiltrates sensitive data (malicious versions 9.9.0, 9.9.9, 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @ceeferenderer/itg-renderer-sdk (npm)
What this malware does
Malicious package due to code obfuscation, dynamic module loading, process exposure, suspicious install script, and untrustworthy author email.
This package performs silent reconnaissance against any machine that installs or requires it. The package.json declares scripts.install = node index.js, and index.js also loads lib/core.js at require() time. lib/core.js obtains the os and dns modules via module.constructor._load(...) — a deliberate bypass of simple require('os')/require('dns') source grep — then reads os.userInfo().username, os.hostname(), and path.basename(process.cwd()), concatenates them with a timestamp and the hard-coded domain oob.sl4x0.xyz, and calls dns.resolve4() on the resulting subdomain. Because oob.sl4x0.xyz is an attacker-controlled authoritative nameserver, the victim's resolver leaks the username, hostname, and working-directory name as DNS query labels. The sensitive identifiers and the domain itself are stored as hex byte arrays in lib/6ad264.js and lib/b02e30.js and reassembled at runtime via String.fromCharCode, and the JS filenames are random hex — clear evasion of static review. Supporting red flags: the author email is [email protected] (same attacker-owned domain), the version is 99.9.9, and the package description is generic. This is active exfiltration of installer-side data executed on both install and import, with no legitimate functionality documented.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for @ceeferenderer/itg-renderer-sdk (3 malicious versions).
If you installed it — respond
@ceeferenderer/itg-renderer-sdk 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.
Did it already run?
If @ceeferenderer/itg-renderer-sdk 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
Campaign
References
Credits
- Amazon Inspector · finder
- ReversingLabs · finder
- SafeDep · finder
Detect & block this
O3 blocks @ceeferenderer/itg-renderer-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.