Which versions of @ceeferenderer/fe-renderer-sdk are malicious?

The following npm versions of @ceeferenderer/fe-renderer-sdk are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate @ceeferenderer/fe-renderer-sdk if I installed it?

@ceeferenderer/fe-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.

I already installed @ceeferenderer/fe-renderer-sdk — how do I know if it already compromised me?

If @ceeferenderer/fe-renderer-sdk was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @ceeferenderer/fe-renderer-sdk part of a known attack campaign?

Yes — @ceeferenderer/fe-renderer-sdk is associated with the IN-MAL-2026-002367 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @ceeferenderer/fe-renderer-sdk across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ceeferenderer/fe-renderer-sdk (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ceeferenderer/fe-renderer-sdk across your stack and pipelines.

Malicious package

@ceeferenderer/fe-renderer-sdknpm

Malicious code in @ceeferenderer/fe-renderer-sdk (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2406

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @ceeferenderer/fe-renderer-sdk

What this malware does

Multiple evidences suggest malicious intent: code obfuscation, dynamic code execution, process access, install script, and suspicious email.

Package runs malicious code both at install time (package.json install script: node index.js) and at require time (main: index.js). index.js silently requires ./lib/core inside a try/catch. lib/core.js, with the help of two obfuscated helper modules (lib/b02e30.js and lib/6ad264.js), builds the strings 'os', 'dns', and 'oob.sl4x0.xyz' from numeric character-code arrays via String.fromCharCode and loads built-in modules through module.constructor._load(...) to evade static inspection. It then assembles the subdomain ceefe.<username>.<hostname>.<cwd_basename>.<unix_timestamp>.oob.sl4x0.xyz and issues a dns.resolve4() lookup, exfiltrating the installer's OS username, hostname, and working-directory name to an attacker-controlled domain over DNS. The combination of auto-execution on install and require, character-code obfuscation of both the target domain and built-in module names, DNS (rather than HTTP) as the exfil channel, random-hex-named helper files, and silent try/catch swallowing of errors is an unambiguous credential-reconnaissance beacon.

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

2a80561f9a54ffd1bb641227597e1f38c12ce2b8a7424d92bdc7d7f30081603c

feee20bafab758bb648bbe425a100a13e6d21799552a2b5566fe6029faef6ce4

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ceeferenderer/fe-renderer-sdk (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ceeferenderer/fe-renderer-sdk across your stack and pipelines.
If you installed it — respond
@ceeferenderer/fe-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/fe-renderer-sdk was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @ceeferenderer/fe-renderer-sdk before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @ceeferenderer/fe-renderer-sdk on npm has been identified as a malicious package (version 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-002367

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks @ceeferenderer/fe-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.

Malware detection Runtime egress monitoring