Which versions of @business_promocode/apply_promocode are malicious?

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

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

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

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

Yes — @business_promocode/apply_promocode is associated with the GHSA-g79w-grhv-qw3m 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/apply_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/apply_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/apply_promocode across your stack and pipelines.

Malicious package

@business_promocode/apply_promocodenpm

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

MAL-2026-3116

Immediate action

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

npm uninstall @business_promocode/apply_promocode

What this malware does

The package @business_promocode/apply_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/apply_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)

53701fead143076e2adc850eb54117a00ffeefac79c7afb64523b4795d8ccaf9

5adac459fd1c8fca06e818942c9a98e6f798828163fadd996266ae7660132ae7

a125aebd95d40f3c0e8a100d2bd82de1f42e3608196c1bc50d6870ebf65628f6

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/apply_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/apply_promocode across your stack and pipelines.
If you installed it — respond
Remove @business_promocode/apply_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/apply_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/apply_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/apply_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-g79w-grhv-qw3m

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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