Which versions of arno-baidu2-test are malicious?

The following npm versions of arno-baidu2-test are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate arno-baidu2-test if I installed it?

Remove arno-baidu2-test 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 activity or persistence.

I already installed arno-baidu2-test — how do I know if it already compromised me?

If arno-baidu2-test 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 arno-baidu2-test part of a known attack campaign?

Yes — arno-baidu2-test is associated with the GHSA-f364-w7ww-jqgr, RLMA-2025-05688 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 arno-baidu2-test 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 arno-baidu2-test (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging arno-baidu2-test across your stack and pipelines.

Malicious package

arno-baidu2-testnpm

arno-baidu2-test is a confirmed malicious npm package (MAL-2025-48923) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in arno-baidu2-test (npm)

MAL-2025-48923

Immediate action

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

npm uninstall arno-baidu2-test

What this malware does

The package arno-baidu2-test was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

380635db26fa9fbaa70b78c6dba294a362a9342cb346a4f0542792c92b7cb76c

131a10e926c682b41b450810caef439af7c7137fa95422b58970a57ff2a2316d

902378e6cba582fb65af3c2d6c9ed28fb2dd90052f9c7caa04b97dae25758e33

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for arno-baidu2-test (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging arno-baidu2-test across your stack and pipelines.
If you installed it — respond
Remove arno-baidu2-test 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 activity or persistence.
Did it already run?
If arno-baidu2-test 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 arno-baidu2-test 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. arno-baidu2-test on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-f364-w7ww-jqgrRLMA-2025-05688

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks arno-baidu2-test-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database