Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@oplus/obus-web-sdk-plugin-recoverynpm

Malicious code in @oplus/obus-web-sdk-plugin-recovery (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5426
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @oplus/obus-web-sdk-plugin-recovery

What this malware does

@oplus/[email protected] publishes to a likely-private internal scope at an artificially high version to win resolution against an organization's internal package. On npm install, scripts/postinstall.js executes automatically and: (1) reads os.userInfo().username, os.hostname(), and process.cwd(); (2) fetches the installer's public IP from api.ipify.org; (3) hex-encodes the collected fields and issues a DNS lookup of <payload>.xjaipnfhcpawuhzlgzkzo1ak3aai9m873.oast.fun, leaking the data via the subdomain label to an interactsh out-of-band C2; (4) base64-encodes the same payload and sends it as an x-poc header in an HTTPS GET to https://xjaipnfhcpawuhzlgzkzo1ak3aai9m873.oast.fun/poc. The file labels itself a 'Dependency Confusion PoC - Bug Bounty Research,' but the runtime behavior is unconditional exfiltration of installer identity to a third-party endpoint, with no opt-out, on every install. Combined with the 99.99.99 version pin against the @oplus scope, this is the classic dependency-confusion attack shape and is harmful to any installer who resolves it.

Malicious versions

1 flagged
99.99.99

Indicators of compromise (SHA-256)

a7435b09e6ec064fe7ff0738becd8dd3445f1a73e97427a8fb9285460bd4f723
c2654b14fdaecfaf92b6ef7c34e19a59779d8997dc755dd1737a5d73abb0a410

Detection & response playbook

Credential / info stealer

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @oplus/obus-web-sdk-plugin-recovery (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @oplus/obus-web-sdk-plugin-recovery across your stack and pipelines.

  2. If you installed it — respond

    @oplus/obus-web-sdk-plugin-recovery 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.

  3. Did it already run?

    If @oplus/obus-web-sdk-plugin-recovery 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.

  4. How O3 protects you

    O3 blocks @oplus/obus-web-sdk-plugin-recovery 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. @oplus/obus-web-sdk-plugin-recovery on npm has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005004IN-MAL-2026-005005

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @oplus/obus-web-sdk-plugin-recovery-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
@oplus/obus-web-sdk-plugin-recovery (npm) malicious package — MAL-2026-5426 | O3 Security