Which versions of conversionvaluemanager are malicious?

The following npm versions of conversionvaluemanager are flagged malicious: 3.0.0. Treat any of these as compromised.

How do I remediate conversionvaluemanager if I installed it?

conversionvaluemanager establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed conversionvaluemanager — how do I know if it already compromised me?

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

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

Malicious package

conversionvaluemanagernpm

conversionvaluemanager is a confirmed malicious npm package (MAL-2026-10084) that opens a backdoor for remote access (malicious version 3.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in conversionvaluemanager (npm)

MAL-2026-10084

Immediate action

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

npm uninstall conversionvaluemanager

What this malware does

On npm install, postinstall.js automatically runs and gathers installer-identifying data (os.hostname(), os.userInfo(), os.platform(), cwd, Node version, timestamp), then sends it as query-string parameters via plain-HTTP GET to a Burp Collaborator subdomain at aq4v2egelzh9n07h3l9d2b5mvd14pvdk.oastify.com/adjust-dep-confusion. The package.json description self-identifies as a dependency-confusion proof-of-concept ("PoC - Dependency Confusion - Bug Bounty by ha4x0r"), and the package name targets an internal/private package name. Any organization whose build misresolves to this public package leaks host, user, and environment identifiers to the third-party Collaborator endpoint on install. PoC/bug-bounty framing does not change the installer-side impact: the beacon fires on every install.

Malicious versions

1 flagged

3.0.0

Indicators of compromise (SHA-256)

21445a74cc1c4d33c89f1a7d8c357c79d5adb11cda135c813676b23c875418e9

8a0866f3469405ec2768c987abf110354927c943f2d2a5303834ff7e6deccf5f

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for conversionvaluemanager (version 3.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging conversionvaluemanager across your stack and pipelines.
If you installed it — respond
conversionvaluemanager establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If conversionvaluemanager 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 conversionvaluemanager 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. conversionvaluemanager on npm has been identified as a malicious package (version 3.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009360RLMA-2026-05522

References

npmjs.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks conversionvaluemanager-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database