What does the 1239i32049i malware do?

Package declares a postinstall script that runs dist/index.js, the sole shipped file, which is heavily obfuscated with javascript-obfuscator (rotated string array, _0xNNNN identifiers, control-flow dispatch). At install time it reads process.env.P, issues an HTTPS GET to https://dropper-crm.vercel.app/api/payload/ , base64-decodes the response body, and executes it via new Function('require', decoded), granting the remote endpoint arbitrary code execution with require access on the installing machine. The package name is a numeric string with no documented functionality, no README, and no legitimate purpose beyond delivery of the remote payload.

Which versions of 1239i32049i are malicious?

The following npm versions of 1239i32049i are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate 1239i32049i if I installed it?

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

If 1239i32049i 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 1239i32049i part of a known attack campaign?

Yes — 1239i32049i is associated with the IN-MAL-2026-014536 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 1239i32049i 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 1239i32049i (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging 1239i32049i across your stack and pipelines.

Malicious package

1239i32049inpm

1239i32049i is a confirmed malicious npm package (MAL-2026-12117) that executes malicious code on install (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in 1239i32049i (npm)

MAL-2026-12117

Immediate action

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

npm uninstall 1239i32049i

What this malware does

Package declares a postinstall script that runs dist/index.js, the sole shipped file, which is heavily obfuscated with javascript-obfuscator (rotated string array, _0xNNNN identifiers, control-flow dispatch). At install time it reads process.env.P, issues an HTTPS GET to https://dropper-crm.vercel.app/api/payload/<P>, base64-decodes the response body, and executes it via new Function('require', decoded), granting the remote endpoint arbitrary code execution with require access on the installing machine. The package name is a numeric string with no documented functionality, no README, and no legitimate purpose beyond delivery of the remote payload.

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

6c99f6d077df7b1209fb59dafa8641b14b3947d321379bc6ad22f2660d3d4c7b

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

Campaign

IN-MAL-2026-014536

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks 1239i32049i-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