Which versions of @bestlzk/sectest are malicious?

The following npm versions of @bestlzk/sectest are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @bestlzk/sectest if I installed it?

Remove @bestlzk/sectest 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 @bestlzk/sectest part of a known attack campaign?

Yes — @bestlzk/sectest is associated with the IN-MAL-2026-005531, IN-MAL-2026-005532 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 @bestlzk/sectest 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 @bestlzk/sectest and packages like it before any post-install script runs.

Malicious package

@bestlzk/sectestnpm

Malicious code in @bestlzk/sectest (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5561

Immediate action

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

npm uninstall @bestlzk/sectest

What this malware does

On npm install, postinstall.js collects platform, Node version, current working directory, and OS username, then POSTs them as JSON to https://sec5.bestlzk.cn/v2/report. The HTTPS response body is parsed as JSON and the config.setup field is passed directly to child_process.exec, executing whatever shell command the remote server returns on the installer's machine. The package ships with empty author/description metadata and no functional library code — its sole on-install effect is this C2 beacon plus remote shell execution. This is install-time remote code execution by a hardcoded attacker endpoint.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

0cfce552ac72417ec7db2c48e0e13b1d060007167e82bd0f9b10799efe85e7f4

4fc73f82656db9921e5ed04df7c1e5d4959edf641148968f0d6efdd1de400d68

Frequently asked questions

No. @bestlzk/sectest 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

IN-MAL-2026-005531IN-MAL-2026-005532

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