openai-agents-helpersnpm
openai-agents-helpers is a confirmed malicious npm package (MAL-2026-6582) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1, 0.2.0…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in openai-agents-helpers (npm)
What this malware does
On npm install, scripts/postinstall.js automatically reads a broad set of installer-side identity and cloud-configuration files — ~/.gitconfig and the parent project's.git/config plus.git/logs/HEAD (committer emails), ~/.config/gh/hosts.yml (GitHub login), every ~/.ssh/*.pub file (key identity comments / emails), ~/.config/gcloud/properties (GCP project and account), ~/.aws/config (profile names and SSO identifiers), /etc/resolv.conf (corporate DNS search domains), os.hostname(), os.userInfo().username, current working directory, and the parent project's package.json. The collected data is bundled into a JSON payload and POSTed via https.request to the hardcoded endpoint https://npm-package-logger-228835561205.europe-west1.run.app/. The package presents itself as a helper for the OpenAI Agents SDK (name openai-agents-helpers, author OpenAI Agents JS Guide, homepage openai-agents-js.guide, depends on @openai/agents), but none of those identifiers are owned by OpenAI — the branding impersonates the official SDK ecosystem to lure developers who are likely to have OpenAI API keys and cloud credentials in their environment. Collection is opt-out (an env var disables it) rather than opt-in, and the destination is not a documented publisher domain. Even with a credential-line skip filter, the exfiltrated data (AWS profile/SSO names, GCP project + account, GitHub login, SSH key identity emails, corporate DNS search domain, hostname, username) is high-value reconnaissance for targeted phishing and follow-on account compromise.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for openai-agents-helpers (25 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging openai-agents-helpers across your stack and pipelines.
If you installed it — respond
openai-agents-helpers 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 openai-agents-helpers 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 openai-agents-helpers 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks openai-agents-helpers-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.