Which versions of confluence-rest are malicious?

The following npm versions of confluence-rest are flagged malicious: 30.0.0. Treat any of these as compromised.

How do I remediate confluence-rest if I installed it?

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

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

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

Malicious package

confluence-restnpm

confluence-rest is a confirmed malicious npm package (MAL-2026-15532) that executes malicious code on install (malicious version 30.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in confluence-rest (npm)

MAL-2026-15532

Immediate action

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

npm uninstall confluence-rest

What this malware does

package.json declares a self-referential dependency whose key equals the package's own name (confluence-rest) and whose value is the bare HTTPS URL https://repo.securityctrl.com/confluence-rest rather than a semver range. On npm install, npm resolves that URL and installs whatever tarball the host returns, running any lifecycle scripts inside it, with no version pin and no integrity check. The shipped index.js is an inert stub, so the manifest URL is the entire code-delivery path for the package. Whoever controls repo.securityctrl.com controls code that executes on the installer's machine at install time, and the self-referential dependency-confusion shape (same name as the published package, version 30.0.0 sufficient to win resolution against a legitimate internal package of the same name) indicates targeting of internal-package resolution.

Malicious versions

1 flagged

30.0.0

Indicators of compromise (SHA-256)

5d314e75faa527b1c10dbc34b2867180fb0726f2547d9b0edd0564aec3e38fd8

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

Campaign

IN-MAL-2026-019106

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks confluence-rest-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