Which versions of eyee are malicious?

The following npm versions of eyee are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate eyee if I installed it?

eyee 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 eyee — how do I know if it already compromised me?

If eyee 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 eyee part of a known attack campaign?

Yes — eyee is associated with the IN-MAL-2026-007048 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 eyee 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 eyee (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eyee across your stack and pipelines.

Malicious package

eyeenpm

eyee is a confirmed malicious npm package (MAL-2026-6189) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eyee (npm)

MAL-2026-6189

Immediate action

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

npm uninstall eyee

What this malware does

On require/run, eyee auto-executes main() (package.json sets main=cdp_inject.js and the bottom of the file invokes main() unless --stop/--detach is passed). main() spawns a detached testpad.exe Chromium with --remote-debugging-port=9222, attaches via the Chrome DevTools Protocol, and injects a script that captures document.body.innerText and the active editor contents from any page the installer has open. Captured questions and the LLM-generated answers are POSTed to a hardcoded Discord webhook (https://discord.com/api/webhooks/1512503888811659355/...) controlled by the author, silently relaying the installer's browser content to a third party. The same scraped content is sent to api.groq.com under one of six hardcoded gsk_... Groq API keys bundled in cdp_inject.js, so the installer's queries are also routed through an author-owned LLM account they did not opt into. Outbound HTTPS to Groq is made with rejectUnauthorized: false, disabling TLS validation on the channel carrying scraped page content and bearer tokens. Process-wide uncaughtException and unhandledRejection handlers swallow errors to keep the loop running quietly. The npm package name (eyee) does not match the README's install instructions (npm install -g cdp-core / npx -y cdp-core), consistent with republishing the same payload under multiple names.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

743696e9409c97e89816b050f0346b86446464fdbaeead6ae49ddabf50a082ba

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 eyee (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eyee across your stack and pipelines.
If you installed it — respond
eyee 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 eyee 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 eyee 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. eyee on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007048

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks eyee-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

Explore

All malware advisories How O3 detects malware Vulnerability database