What does the baidu-src-test3 malware do?

The package baidu-src-test3 was found to contain malicious code. The OpenSSF Package Analysis project identified 'baidu-src-test3' @ 0.0.4 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of baidu-src-test3 are malicious?

The following npm versions of baidu-src-test3 are flagged malicious: 0.0.4. Treat any of these as compromised.

How do I remediate baidu-src-test3 if I installed it?

Remove baidu-src-test3 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 baidu-src-test3 — how do I know if it already compromised me?

If baidu-src-test3 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find baidu-src-test3 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for baidu-src-test3 (version 0.0.4).

Malicious package

baidu-src-test3npm

Advisory published Nov 25, 2025Updated Dec 1, 2025

baidu-src-test3 is a confirmed malicious npm package (MAL-2025-191461) that executes malicious code on install (malicious version 0.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in baidu-src-test3 (npm)

MAL-2025-191461

Immediate action

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

npm uninstall baidu-src-test3

What this malware does

The package baidu-src-test3 was found to contain malicious code.

The OpenSSF Package Analysis project identified 'baidu-src-test3' @ 0.0.4 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

0.0.4

Indicators of compromise (SHA-256)

e50d8f616942eb8beb76f6019780078fb1bc2d6219cc6128c56e311bc5d77a83

b41154fc2678ab5be471f8ef4eb2065a74e9310ea81b5d3f3fd8617a1e880d67

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for baidu-src-test3 (version 0.0.4).
If you installed it — respond
Remove baidu-src-test3 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 baidu-src-test3 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. baidu-src-test3 on npm has been identified as a malicious package (version 0.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks baidu-src-test3-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