Which versions of @oplus/obus-web-sdk are malicious?

The following npm versions of @oplus/obus-web-sdk are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate @oplus/obus-web-sdk if I installed it?

Remove @oplus/obus-web-sdk from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is @oplus/obus-web-sdk part of a known attack campaign?

Yes — @oplus/obus-web-sdk is associated with the IN-MAL-2026-005007, IN-MAL-2026-005006 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect @oplus/obus-web-sdk in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking @oplus/obus-web-sdk and packages like it before any post-install script runs.

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

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

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection