Which versions of 33-js-concepts are malicious?

The following npm versions of 33-js-concepts are flagged malicious: 6.0.2. Treat any of these as compromised.

How do I remediate 33-js-concepts if I installed it?

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

If 33-js-concepts 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 33-js-concepts part of a known attack campaign?

Yes — 33-js-concepts is associated with the RLMA-2024-00280, RLUA-2024-06094, RLUA-2026-05952 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 33-js-concepts 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 33-js-concepts (version 6.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging 33-js-concepts across your stack and pipelines.

Malicious package

33-js-conceptsnpm

33-js-concepts is a confirmed malicious npm package (MAL-2024-1700) that executes malicious code on install (malicious version 6.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in 33-js-concepts (npm)

MAL-2024-1700

Immediate action

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

npm uninstall 33-js-concepts

Malicious versions

1 flagged

6.0.2

Indicators of compromise (SHA-256)

eb6a441a3b8119a1e6d617680ca7ecc98cbea884b38caca6d30b050902e0982f

ed95397ce464a88806db3f9a837bf6198c09cf8e0bffcf584e13f6a46573b600

0afb47c686eb21b5c86ad61957ae625665122480ce5cbc897ad97bd770cbb0ae

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

Campaign

RLMA-2024-00280RLUA-2024-06094RLUA-2026-05952

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks 33-js-concepts-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

Explore

All malware advisories How O3 detects malware Vulnerability database