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

frontend-js-state-webnpm

Malicious code in frontend-js-state-web (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-680
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall frontend-js-state-web

What this malware does

The package frontend-js-state-web 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

3 flagged
2.2.22.2.32.2.4

Indicators of compromise (SHA-256)

51c22459a93136b9447c4dcb2499c883e75891f292b491550cbef23f8e3224bf
770e7ef9c670e6c188650363a084728f7827f49ab63d6fb9aa57f6e4cfd07dbf
39534cea536e1d50370eb0f9db50e9381f4ee96bb71e831013da9b76f2d30742
412306ccd33b4d5b34a95ee3b8e8701c065228f76ff8e5ec534acb60af2c1282

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 frontend-js-state-web (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging frontend-js-state-web across your stack and pipelines.

  2. If you installed it — respond

    Remove frontend-js-state-web 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 frontend-js-state-web 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 frontend-js-state-web 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. frontend-js-state-web on npm has been identified as a malicious package (versions 2.2.2, 2.2.3, 2.2.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-xj8r-jcfw-rgh6RLMA-2026-01331RLUA-2026-01950

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks frontend-js-state-web-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
frontend-js-state-web (npm) malicious package — MAL-2026-680 | O3 Security