Which versions of babel-preset-current-node-syntax are malicious?

The following PyPI versions of babel-preset-current-node-syntax are flagged malicious: 2.1.1. Treat any of these as compromised.

How do I remediate babel-preset-current-node-syntax if I installed it?

babel-preset-current-node-syntax is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed babel-preset-current-node-syntax — how do I know if it already compromised me?

If babel-preset-current-node-syntax 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 babel-preset-current-node-syntax part of a known attack campaign?

Yes — babel-preset-current-node-syntax is associated with the RLMA-2025-03545, GENERIC-questionable-pentest, RLUA-2026-00133 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 babel-preset-current-node-syntax 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 babel-preset-current-node-syntax (version 2.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging babel-preset-current-node-syntax across your stack and pipelines.

Malicious package

babel-preset-current-node-syntaxPyPI

Malicious code in babel-preset-current-node-syntax (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-6460

Immediate action

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

pip uninstall babel-preset-current-node-syntax

What this malware does

Generic campaign for all (likely) research / pentests, where the amount or art of collected data raises questions about the privacy, security and ethical side.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: GENERIC-questionable-pentest

Reasons (based on the campaign):

exfiltration-env-variables
exfiltration-generic
The package overrides the install command in setup.py to execute malicious code during installation.
typosquatting

Malicious versions

1 flagged

2.1.1

Indicators of compromise (SHA-256)

43f6cb319ca0835689fd03f2d2f7a9e27baff475faaeebefbf76d08b7f80dfbe

f6857c9d628c7ca66d782db1646baaa5cbc6170ea914beac846c7572bfb07cdd

227436e7c8f26da0ff88db12bd9102d85f9f596cf495b6e9192c634d275a5686

1eb3de37b04cf075b9535570800e665e132e0c40c1b59bdfbf8c4e9375a78fa5

495ad126b322f1d6b89bfbc8ca9caf11403c5554271fe178c18776d07cd8718f

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for babel-preset-current-node-syntax (version 2.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging babel-preset-current-node-syntax across your stack and pipelines.
If you installed it — respond
babel-preset-current-node-syntax is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If babel-preset-current-node-syntax 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 babel-preset-current-node-syntax 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. babel-preset-current-node-syntax on PyPI has been identified as a malicious package (version 2.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-03545GENERIC-questionable-pentestRLUA-2026-00133

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks babel-preset-current-node-syntax-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring