Which versions of oj-sp-css-additions are malicious?

Every published version of oj-sp-css-additions on npm is considered malicious. Remove the package entirely.

How do I remediate oj-sp-css-additions if I installed it?

Remove oj-sp-css-additions 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 oj-sp-css-additions — how do I know if it already compromised me?

If oj-sp-css-additions 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 oj-sp-css-additions part of a known attack campaign?

Yes — oj-sp-css-additions is associated with the GHSA-x2r2-5qgq-gv97 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 oj-sp-css-additions 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 oj-sp-css-additions (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging oj-sp-css-additions across your stack and pipelines.

Malicious package

oj-sp-css-additionsnpm

Malicious code in oj-sp-css-additions (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-64

Immediate action

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

npm uninstall oj-sp-css-additions

What this malware does

The package oj-sp-css-additions 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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

c37d90fb6caa26e5750aa534586bd17e2b14e0d80a481a167a55276e6be95570

76f44dd1651a643e28e082a676732a19e8a8a8fcf5b2f88264aa47c7f5e31dce

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

Campaign

GHSA-x2r2-5qgq-gv97

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks oj-sp-css-additions-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