Which versions of hehehe are malicious?

The following npm versions of hehehe are flagged malicious: 2.0.2. Treat any of these as compromised.

How do I remediate hehehe if I installed it?

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

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

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

Malicious package

hehehenpm

Malicious code in hehehe (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10732

Immediate action

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

npm uninstall hehehe

What this malware does

Package is published as an 'enterprise Windows Diagnostic Utility' but is an anti-proctoring cheating tool that also steals the installer's browser session cookies. main.js invokes a bundled PowerShell routine that opens Chrome, Edge, and Brave 'Local State' files, decrypts the DPAPI-wrapped AES-256-GCM key, and reads each browser's Cookies SQLite database to extract cookies for.openai.com,.chatgpt.com, auth.openai.com, and auth0.openai.com; the decrypted cookies are then injected into the tool's own Electron session to hijack the installer's ChatGPT login. The bin launcher copies electron.exe to 'SearchFilterHost.exe' inside electron/dist to masquerade as a signed Windows Search subsystem process, spawns a detached background watchdog that respawns with random jitter when killed, and uses SetWindowDisplayAffinity WDA_EXCLUDEFROMCAPTURE plus a '--seb-child' Safe Exam Browser migration path to evade Testpad/AMCAT/SEB proctoring. Ships an undocumented 27MB Windows PE binary bin/uia_extract.exe that main.js executes via python "${pyPath}" || "${exePath}" with no hash or signature verification. SECTION_PROMPTS constants for AMCAT sections (GEN/DEB/APT/PRG) and a 'FINAL ANSWER:' extraction contract confirm the cheating-tool payload behind the diagnostic cover story.

Malicious versions

1 flagged

2.0.2

Indicators of compromise (SHA-256)

588dd776720f805d7d84a58c93ffcd21ed860e3fc21a48787d732eb6180b974d

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

Campaign

IN-MAL-2026-010748

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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