Which versions of billing-paywidget are malicious?

The following npm versions of billing-paywidget are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate billing-paywidget if I installed it?

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

If billing-paywidget 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.

Is billing-paywidget part of a known attack campaign?

Yes — billing-paywidget is associated with the GHSA-3cww-22qr-fgwc, RLMA-2026-01895 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find billing-paywidget across my projects, lockfiles, and CI pipelines?

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

Malicious package

billing-paywidgetnpm

Malicious code in billing-paywidget (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2638

Immediate action

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

npm uninstall billing-paywidget

What this malware does

The package billing-paywidget 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

1 flagged

99.0.0

Indicators of compromise (SHA-256)

9fb345d363e1ea68a00cab458747bd944904e49e476abc0480a5d797f16301d6

106abcc82e6829ef210ead1f7cee43d8804691967d0049649acd2ba53e5dbfa1

8a1d045f893bda154c8f1c451045b34000b97a678cef9952b2dc3ba2f1c83db2

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for billing-paywidget (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging billing-paywidget across your stack and pipelines.
If you installed it — respond
Remove billing-paywidget 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 billing-paywidget 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.
How O3 protects you
O3 blocks billing-paywidget 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. billing-paywidget on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3cww-22qr-fgwcRLMA-2026-01895

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks billing-paywidget-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