Which versions of openaiwrapper are malicious?

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

How do I remediate openaiwrapper if I installed it?

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

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

Yes — openaiwrapper is associated with the IN-MAL-2026-010514 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 openaiwrapper across my projects, lockfiles, and CI pipelines?

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

Malicious package

openaiwrappernpm

Advisory published Jul 14, 2026Updated Jul 14, 2026

openaiwrapper is a confirmed malicious npm package (MAL-2026-10590) 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 openaiwrapper (npm)

MAL-2026-10590

Immediate action

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

npm uninstall openaiwrapper

What this malware does

The package's postinstall lifecycle hook runs.init.js, which reads a hardcoded list of credential-shaped environment variables (including NPM_TOKEN, GITHUB_TOKEN, AWS_SECRET_ACCESS_KEY, STRIPE_, DB_PASSWORD, and other cloud/service tokens) and reads credential files under the user's home directory (~/.npmrc, ~/.env, config.json, credentials.json, and token/secret files under ~/.config). It also collects host identifiers (hostname, platform, cwd, pid). The collected data is serialized and POSTed via https to the hardcoded endpoint https://webhook.cool/at/tender-deer-80/. This fires automatically on npm install with no user opt-in, and the package's name suggests it is impersonating an OpenAI client library.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

ea3d691208e7e5c443aa161241ca12c9b3eacb1b04428f886ea8c5fbec5a4d0c

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for openaiwrapper (version 1.0.0).
If you installed it — respond
openaiwrapper 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 openaiwrapper 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. openaiwrapper 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-010514

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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