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

@helloflex/widget-next-sdknpm

Malicious code in @helloflex/widget-next-sdk (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-760
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @helloflex/widget-next-sdk

What this malware does

The package @helloflex/widget-next-sdk 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

4 flagged
0.0.1-security11.11.1111.11.1211.11.13

Indicators of compromise (SHA-256)

a46cfee6c9ddbc1cd14ba82586192c01f8de3380e0fab15de251aeb801e0b11d
0ca9fce3cc7390ed9fa54426eb0404651c2679a146b83aaf537d0d4c4cf9ba2c
c5dd26e1f409d15273d59963bb1604b5a0289f7d6522014b964eaf1d1172598e

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 @helloflex/widget-next-sdk (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @helloflex/widget-next-sdk across your stack and pipelines.

  2. If you installed it — respond

    Remove @helloflex/widget-next-sdk 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 @helloflex/widget-next-sdk 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 @helloflex/widget-next-sdk 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. @helloflex/widget-next-sdk on npm has been identified as a malicious package (versions 0.0.1-security, 11.11.11, 11.11.12, 11.11.13 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-h3g9-hf4q-p76hRLMA-2026-01015

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @helloflex/widget-next-sdk-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.