Which versions of dojo-rn-interview are malicious?

The following npm versions of dojo-rn-interview are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate dojo-rn-interview if I installed it?

dojo-rn-interview 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 dojo-rn-interview — how do I know if it already compromised me?

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

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

Malicious package

dojo-rn-interviewnpm

dojo-rn-interview is a confirmed malicious npm package (MAL-2026-13549) that opens a backdoor for remote access (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dojo-rn-interview (npm)

MAL-2026-13549

Immediate action

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

npm uninstall dojo-rn-interview

What this malware does

[email protected] declares a preinstall script that runs index.js on npm install. The script collects host identifiers via os.hostname(), os.userInfo(), os.homedir(), __dirname, and DNS server list, and reads the installer's /etc/passwd and /etc/hosts files, then POSTs the collected data over HTTPS to the hardcoded Burp Collaborator subdomain kqepxa9s4krgw7e7b6f7kufiy943stgi.oastify.com. The package name and behavior are consistent with a dependency-confusion reconnaissance beacon targeting internal build systems.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

42dcf2c659fc0c8b63b90671ae2a865a7811d5eeaaf321aab8355358117be47d

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

Campaign

IN-MAL-2026-017053

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dojo-rn-interview-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