Which versions of @finxsecdemo/utils are malicious?

The following npm versions of @finxsecdemo/utils are flagged malicious: 1.0.2, 1.0.3. Treat any of these as compromised.

How do I remediate @finxsecdemo/utils if I installed it?

@finxsecdemo/utils 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 @finxsecdemo/utils — how do I know if it already compromised me?

If @finxsecdemo/utils 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 @finxsecdemo/utils part of a known attack campaign?

Yes — @finxsecdemo/utils is associated with the IN-MAL-2026-012879, IN-MAL-2026-017914 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 @finxsecdemo/utils 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 @finxsecdemo/utils (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @finxsecdemo/utils across your stack and pipelines.

Malicious package

@finxsecdemo/utilsnpm

@finxsecdemo/utils is a confirmed malicious npm package (MAL-2026-11170) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.2, 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @finxsecdemo/utils (npm)

MAL-2026-11170

Immediate action

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

npm uninstall @finxsecdemo/utils

What this malware does

The postinstall.js lifecycle script unconditionally issues an HTTPS GET and a DNS resolution against a hardcoded interact.sh/OAST subdomain (llhvrrffsffmousfvteqie2heq3c7rl55.oast.fun) on every install, reading os.hostname(), os.userInfo(), and process.env in the surrounding code. The beacon fires on npm install and reports the installer's source IP and DNS resolver IP to whoever owns the OAST token, giving them an enumeration list of hosts on which the package landed. The package's own main returns a formatCurrency string containing '[DEPENDENCY-CONFUSION-POC: this ran from the PUBLIC npm registry, not @finxsecdemo private packages]', which corrupts any consumer that displays formatted currency. Console framing as a 'dependency confusion PoC' is author-controlled labeling; the network callback and output corruption occur regardless.

The OpenSSF Package Analysis project identified '@finxsecdemo/utils' @ 1.0.2 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

1.0.21.0.3

Indicators of compromise (SHA-256)

f6ca8fa85d211056af32639b18f95f13c362b2764d85c812e6741d6747abf94d

be118b4cf0acab2c331cc37f68a19bdbdf2ac8423ef984a1cac5c9f4d21c1e7e

09fd53bc90d2931d4d9df72d8b2fa1205304486913a9e87494dbe72fa51c40fa

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

Campaign

IN-MAL-2026-012879IN-MAL-2026-017914

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @finxsecdemo/utils-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

Explore

All malware advisories How O3 detects malware Vulnerability database