Which versions of @business_promocode/cancel_promocode are malicious?

The following npm versions of @business_promocode/cancel_promocode are flagged malicious: 99.0.3. Treat any of these as compromised.

How do I remediate @business_promocode/cancel_promocode if I installed it?

Remove @business_promocode/cancel_promocode 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 @business_promocode/cancel_promocode — how do I know if it already compromised me?

If @business_promocode/cancel_promocode 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 @business_promocode/cancel_promocode part of a known attack campaign?

Yes — @business_promocode/cancel_promocode is associated with the GHSA-5vjv-9xjr-hq87 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 @business_promocode/cancel_promocode 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 @business_promocode/cancel_promocode (version 99.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @business_promocode/cancel_promocode across your stack and pipelines.

Malicious package

@business_promocode/cancel_promocodenpm

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

MAL-2026-3117

Immediate action

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

npm uninstall @business_promocode/cancel_promocode

What this malware does

The package @business_promocode/cancel_promocode 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.

The OpenSSF Package Analysis project identified '@business_promocode/cancel_promocode' @ 99.0.3 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

99.0.3

Indicators of compromise (SHA-256)

a5b5e7e0dccb947f83409dee4c6c0c086dd345eaa0200c6f048f89e0b6d181b1

002798d60b98859a68bc9daf0ebaf7794b8d83973b69fb4c8bfe9979f685e51d

a7d53b76fbde4e77271ad63fac4e28c773e117ae8a26d00c2c97faa848dfe369

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 @business_promocode/cancel_promocode (version 99.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @business_promocode/cancel_promocode across your stack and pipelines.
If you installed it — respond
Remove @business_promocode/cancel_promocode 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 @business_promocode/cancel_promocode 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 @business_promocode/cancel_promocode 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. @business_promocode/cancel_promocode on npm has been identified as a malicious package (version 99.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-5vjv-9xjr-hq87

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @business_promocode/cancel_promocode-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