@ceeferenderer/fe-renderer-sdk
Enterprise-grade utilities for production JavaScript applications with comprehensive validation, error handling, and cross-environment compatibility.
This report shows the evidence for @ceeferenderer/fe-renderer-sdk@99.9.9. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiSource inspection confirms covert DNS exfiltration of host/project identifiers at install time and import time, implemented through obfuscated helper files and unrelated to package functionality. This is concrete malicious behavior, not a noisy static hint.
Decision evidence
public snapshot- package.json defines install lifecycle: "install": "node index.js".
- index.js import-time executes ./lib/core inside a swallowed try/catch before exporting utilities.
- lib/core.js collects os.userInfo().username, os.hostname(), and process.cwd() basename.
- lib/core.js builds a DNS query with those values plus timestamp and cfg.dom.
- lib/b02e30.js decodes cfg.dom to oob.sl4x0.xyz; lib/6ad264.js hides loading os/dns/process via module.constructor._load.
- src/validation.js, src/formatting.js, src/transformation.js, and src/errors.js are ordinary utility code.
- No credential file reads, shell execution, persistence, or destructive filesystem writes observed.
Source & flagged code
1 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @ceeferenderer/fe-renderer-sdk@99.9.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing @ceeferenderer/fe-renderer-sdk@99.9.9. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.