Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

jest-test-plugin-utilsnpm

jest-test-plugin-utils is a confirmed malicious npm package (MAL-2026-5896) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jest-test-plugin-utils (npm)

MAL-2026-5896
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall jest-test-plugin-utils

What this malware does

The package advertises itself as a Jest plugin (name: 'jest-test-plugin-utils', description: 'mqtt utils') but ships no Jest or MQTT functionality. Its main entry dist/index.js is a heavily obfuscated 200KB browserify bundle (obfuscator.io fingerprint: 1299-entry rotated string array, decoder wrapper, control-flow flattening; built with the declared devDependency 'gulp-javascript-obfuscator'). After deobfuscation, the only meaningful behavior is a function loadFilbetScriptSilently() (exposed as window.fetchFilbetScript) that creates a <script> element with src='https://cdn.jsdelivr.net/gh/gongben2024/network-security@main/src/filbet.js' and appends it to document.head, executing whatever code the author hosts at that mutable @main branch. The destination repository is named 'network-security' under author 'gongben2024' and is unrelated to the package's stated purpose. Because the reference is to the @main branch (not a pinned commit/tag), the author can change the executed payload at any time without republishing this package. Any application that bundles or imports this module will execute attacker-controlled JavaScript in the browser context, with full access to the host page's DOM, cookies, and storage. The combination of name camouflage, heavy obfuscation, and unpinned remote-script execution is a deliberate supply-chain attack pattern.

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

5 flagged
1.0.01.0.11.0.21.0.31.0.4

Indicators of compromise (SHA-256)

3f948eff13632557a65152c587b6aa87783e49cf40504aedca8ee15da6ed205e
54c5196f3361da72dfccd2c8abb0caba132415f9907602c5a6ec92d6da2e077f
bb80fa98045e0dd75514425f419aa986e7e57bfa888d8baaa8c5eb0016418f83
f5445eba984ab32829120583a68c6bfc2fa8aec2f875b506c873de598f1d27d1
951d82ab1573c962c8c548477013f418229d33a24e4e6a89e509ca4fdb149106
149fc5043ae3e73f200138c8c6c88106df7b187c2e08d6ad0dc7e889721de28b

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for jest-test-plugin-utils (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jest-test-plugin-utils across your stack and pipelines.

  2. If you installed it — respond

    Remove jest-test-plugin-utils 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.

  3. Did it already run?

    If jest-test-plugin-utils 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.

  4. How O3 protects you

    O3 blocks jest-test-plugin-utils 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. jest-test-plugin-utils on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006765IN-MAL-2026-006764IN-MAL-2026-006766IN-MAL-2026-006763GHSA-7969-jc8h-fp32IN-MAL-2026-018464

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks jest-test-plugin-utils-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.

Explore

jest-test-plugin-utils (npm) malicious package — MAL-2026-5896 | O3 Security