Which versions of oclif-dev are malicious?

The following npm versions of oclif-dev are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate oclif-dev if I installed it?

oclif-dev 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 oclif-dev — how do I know if it already compromised me?

If oclif-dev 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 oclif-dev part of a known attack campaign?

Yes — oclif-dev is associated with the RLMA-2025-05100, RLUA-2025-05899 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 oclif-dev 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 oclif-dev (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging oclif-dev across your stack and pipelines.

Malicious package

oclif-devnpm

oclif-dev is a confirmed malicious npm package (MAL-2025-42049) that steals credentials and exfiltrates sensitive data (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in oclif-dev (npm)

MAL-2025-42049

Immediate action

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

npm uninstall oclif-dev

What this malware does

The package oclif-dev was found to contain malicious code.

This package installs a dependency hosted on a custom domain that runs an info stealer during installation. The info stealer focuses on stealing npm, git, and other CI/CD related tokens.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

10cfeb2505ac779f44f00756dd80ffbab895892b867d7a5d23748259c01832f8

9cf078178f5da45231528dbb9bb1883266f18b9c8cd4784a7c8542a3c3d4de7b

a2e897b4dcc2503c353e7c0b2ef1df695b3b86a4b03841a9005620b6ba2e776a

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 oclif-dev (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging oclif-dev across your stack and pipelines.
If you installed it — respond
oclif-dev 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 oclif-dev 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 oclif-dev 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. oclif-dev on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05100RLUA-2025-05899

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks oclif-dev-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