@ceeferenderer/itg-renderer-sdk
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-3v4h-w4g3-h6r2
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in @ceeferenderer/itg-renderer-sdk (npm)
Malicious package due to code obfuscation, dynamic module loading, process exposure, suspicious install script, and untrustworthy author email.
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (51b9fa22264e38705c3a7ba319515ee66036e72ab14c32d08b01a5695aa191b8)
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.
Source: ghsa-malware (6f92dd8051377efd8dfa110522007ece62bb14b80bd796e5beb3f93de6d8bdf5)
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.
Not rated by the source.
0 (semver)None 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