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?

Remove eyee from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed eyee — how do I know if it already compromised me?

If eyee 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.

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?

Search your lockfiles and build artifacts for eyee (version 1.0.0).

Malicious package

eyeenpm

Advisory published Jun 19, 2026Updated Jun 19, 2026

eyee is a confirmed malicious npm package (MAL-2026-6189) that executes malicious code on install (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

Malicious package

Find it
Search your lockfiles and build artifacts for eyee (version 1.0.0).
If you installed it — respond
Remove eyee from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If eyee 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

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 malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database