Which versions of @osl-design/react are malicious?

The following npm versions of @osl-design/react are flagged malicious: 9.9.10. Treat any of these as compromised.

How do I remediate @osl-design/react if I installed it?

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

If @osl-design/react 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.

Is @osl-design/react part of a known attack campaign?

Yes — @osl-design/react is associated with the IN-MAL-2026-020507 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 @osl-design/react across my projects, lockfiles, and CI pipelines?

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

Malicious package

@osl-design/reactnpm

@osl-design/react is a confirmed malicious npm package (MAL-2026-17155) that steals credentials and exfiltrates sensitive data (malicious version 9.9.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @osl-design/react (npm)

MAL-2026-17155

Immediate action

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

npm uninstall @osl-design/react

What this malware does

The package declares "install": "node index.js" in package.json, so npm install automatically executes its top-level script. That script loads runtime/support/telemetry/probe/impl.js, which reads the installer's OS username (os.userInfo().username), hostname (os.hostname()), and current working-directory basename, concatenates them with a prefix into a DNS label, and issues a dns.resolve4 query against the hardcoded domain oob.algamil7x.xyz — a DNS out-of-band exfiltration channel. Sensitive strings, including the module names os/dns, the API names userInfo/hostname/cwd/resolve4, the label prefix osldr, and the destination domain oob.algamil7x.xyz, are hidden as hex/char-code arrays decoded at runtime, and os and dns are loaded through module.constructor._load(...) rather than literal require() calls to evade static analysis. The README contradicts the shipped behavior by asserting the package has no file system access and no network requests beyond registry probes, and the scope name @osl-design/react resembles a design-system package to lend plausibility. Installing this package leaks host-identifying information about the installer's machine to an attacker-controlled DNS resolver.

Malicious versions

1 flagged

9.9.10

Indicators of compromise (SHA-256)

0a3237fada0f96b2160cb8adea5c7734951ca960f71f3f4bf788fec9446b6d3b

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @osl-design/react (version 9.9.10). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @osl-design/react across your stack and pipelines.
If you installed it — respond
@osl-design/react 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 @osl-design/react 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.
How O3 protects you
O3 blocks @osl-design/react 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. @osl-design/react on npm has been identified as a malicious package (version 9.9.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020507

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @osl-design/react-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