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

@oplus/obus-web-sdknpm

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

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

What this malware does

On npm install, the package's scripts/postinstall.js collects the installer's username (os.userInfo()), hostname (os.hostname()), current working directory (process.cwd()), and public IP (fetched from https://api.ipify.org), then exfiltrates the data to a hardcoded interactsh C2 subdomain xjaipnfhcpawuhzlgzkzo1ak3aai9m873.oast.fun through two channels: a DNS lookup with the hex-encoded payload as a subdomain, and an HTTPS GET to /poc carrying the data base64-encoded in an x-poc header. The package uses the @oplus scope (impersonating OPlus/Oppo internal namespaces) and is published at version 99.99.99 — the canonical dependency-confusion pattern designed to outrank any legitimate internal release during resolution. The in-source comment framing this as a benign PoC does not change the installer-side harm: any build that resolves @oplus/obus-web-sdk against the public registry will leak host/user/IP/cwd to attacker infrastructure.

Malicious versions

1 flagged
99.99.99

Indicators of compromise (SHA-256)

870118deab21abae390aabf8c29ffc8e0b29bb14fa1ebc9d66b5c673c5680e12
956ecc19633177f7ef9b458e6407ffbba6c8366688249c07bfd7f3c8e85c17a9

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 (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 across your stack and pipelines.

  2. If you installed it — respond

    @oplus/obus-web-sdk 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 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 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 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-005007IN-MAL-2026-005006

References

Credits

  • Amazon Inspector · finder

Detect & block this

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