human: Given a node-centered hypergraph: <hypergraph>, where nodes represent papers and hyperedges represent sets of papers co-cited by a source paper.

Details of the hypergraph:
Center node: "rowhammer js a remote software induced fault attack in javascript"
  Abstract: A fundamental assumption in software security is that a memory location can only be modified by processes that may write to this memory location. However, a recent study has shown that parasitic effects in DRAM can change the content of a memory cell without accessing it, but by accessing other memory locations in a high frequency. This so-called Rowhammer bug occurs in most of today's memory modules and has fatal consequences for the security of all affected systems, e.g., privilege escalation attacks. #R##N#All studies and attacks related to Rowhammer so far rely on the availability of a cache flush instruction in order to cause accesses to DRAM modules at a sufficiently high frequency. We overcome this limitation by defeating complex cache replacement policies. We show that caches can be forced into fast cache eviction to trigger the Rowhammer bug with only regular memory accesses. This allows to trigger the Rowhammer bug in highly restricted and even scripting environments. #R##N#We demonstrate a fully automated attack that requires nothing but a website with JavaScript to trigger faults on remote hardware. Thereby we can gain unrestricted access to systems of website visitors. We show that the attack works on off-the-shelf systems. Existing countermeasures fail to protect against this new Rowhammer attack.

Connected through hyperedge HE-1 (induced by source paper "are we susceptible to rowhammer an end to end methodology for cloud providers"):
  with members:
    - "rowhammer a retrospective"
    - "spoiler speculative load hazards boost rowhammer and cache attacks"
    - "nethammer inducing rowhammer faults through network requests"
    - "pointing in the right direction securing memory accesses in a faulty world"
    - "another flip in the wall of rowhammer defenses"
    - "the rowhammer problem and other issues we may face as memory becomes denser"
    - "can t touch this practical and generic software only defenses against rowhammer attacks"
    - "drama exploiting dram addressing for cross cpu attacks"

Connected through hyperedge HE-2 (induced by source paper "telehammer cross privilege boundary rowhammer through implicit accesses"):
  with members:
    - "cattmew defeating software only physical kernel isolation"
    - "nethammer inducing rowhammer faults through network requests"
    - "another flip in the wall of rowhammer defenses"
    - "drama exploiting dram addressing for cross cpu attacks"

Connected through hyperedge HE-3 (induced by source paper "terminal brain damage exposing the graceless degradation in deep neural networks under hardware fault attacks"):
  with members:
    - "page cache attacks"
    - "scalable methods for 8 bit training of neural networks"
    - "fine pruning defending against backdooring attacks on deep neural networks"
    - "sever a robust meta algorithm for stochastic optimization"
    - "breaking transferability of adversarial samples with randomness"
    - "turning your weakness into a strength watermarking deep neural networks by backdooring"
    - "training deep neural networks with 8 bit floating point numbers"
    - "nethammer inducing rowhammer faults through network requests"

Connected through hyperedge HE-4 (induced by source paper "processing data where it makes sense enabling in memory computation"):
  with members:
    - "enabling the adoption of processing in memory challenges mechanisms future research directions"
    - "architectural techniques for improving nand flash memory reliability"
    - "what your dram power models are not telling you lessons from a detailed experimental study"
    - "techniques for shared resource management in systems with throughput processors"
    - "errors in flash memory based solid state drives analysis mitigation and recovery"
    - "the rowhammer problem and other issues we may face as memory becomes denser"
    - "error characterization mitigation and recovery in flash memory based solid state drives"
    - "using ecc dram to adaptively increase memory capacity"

Connected through hyperedge HE-5 (induced by source paper "context leakage free transient execution"):
  with members:
    - "fallout reading kernel writes from user space"
    - "spectre is here to stay an analysis of side channels and speculative execution"
    - "store to leak forwarding leaking data on meltdown resistant cpus"
    - "zombieload cross privilege boundary data sampling"
    - "speculative buffer overflows attacks and defenses"
    - "netspectre read arbitrary memory over network"
    - "safespec banishing the spectre of a meltdown with leakage free speculation"
    - "meltdownprime and spectreprime automatically synthesized attacks exploiting invalidation based coherence protocols"

Connected through hyperedge HE-6 (induced by source paper "rowhammer a retrospective"):
  with members:
    - "processing data where it makes sense enabling in memory computation"
    - "rowhammer and beyond"
    - "improving 3d nand flash memory lifetime by tolerating early retention loss and process variation"
    - "d range using commodity dram devices to generate true random numbers with low latency and high throughput"
    - "nethammer inducing rowhammer faults through network requests"
    - "pointing in the right direction securing memory accesses in a faulty world"
    - "what your dram power models are not telling you lessons from a detailed experimental study"
    - "theory and practice of finding eviction sets"

Connected through hyperedge HE-7 (induced by source paper "large scale studies of memory storage and network failures in a modern data center"):
  with members:
    - "architectural techniques for improving nand flash memory reliability"
    - "improving 3d nand flash memory lifetime by tolerating early retention loss and process variation"
    - "d range using commodity dram devices to generate true random numbers with low latency and high throughput"
    - "nethammer inducing rowhammer faults through network requests"
    - "what your dram power models are not telling you lessons from a detailed experimental study"
    - "banshee bandwidth efficient dram caching via software hardware cooperation"
    - "another flip in the wall of rowhammer defenses"
    - "the rowhammer problem and other issues we may face as memory becomes denser"

Connected through hyperedge HE-8 (induced by source paper "fortuneteller predicting microarchitectural attacks via unsupervised deep learning"):
  with members:
    - "fallout reading kernel writes from user space"
    - "zombieload cross privilege boundary data sampling"
    - "undermining user privacy on mobile devices using ai"
    - "tiresias predicting security events through deep learning"
    - "ret2spec speculative execution using return stack buffers"
    - "microwalk a framework for finding side channels in binaries"
    - "state of the art speech recognition with sequence to sequence models"
    - "generic black box end to end attack against state of the art api call based malware classifiers"

Question: Please tell me which class the center node belongs to. The 40 classes are: cs.NA(Numerical Analysis), cs.MM(Multimedia), cs.LO(Logic in Computer Science), cs.CY(Computers and Society), cs.CR(Cryptography and Security), cs.DC(Distributed, Parallel, and Cluster Computing), cs.HC(Human-Computer Interaction), cs.CE(Computational Engineering, Finance, and Science), cs.NI(Networking and Internet Architecture), cs.CC(Computational Complexity), cs.AI(Artificial Intelligence), cs.MA(Multiagent Systems), cs.GL(General Literature), cs.NE(Neural and Evolutionary Computing), cs.SC(Symbolic Computation), cs.AR(Hardware Architecture), cs.CV(Computer Vision and Pattern Recognition), cs.GR(Graphics), cs.ET(Emerging Technologies), cs.SY(Systems and Control), cs.CG(Computational Geometry), cs.OH(Other Computer Science), cs.PL(Programming Languages), cs.SE(Software Engineering), cs.LG(Machine Learning), cs.SD(Sound), cs.SI(Social and Information Networks), cs.RO(Robotics), cs.IT(Information Theory), cs.PF(Performance), cs.CL(Computation and Language), cs.IR(Information Retrieval), cs.MS(Mathematical Software), cs.FL(Formal Languages and Automata Theory), cs.DS(Data Structures and Algorithms), cs.OS(Operating Systems), cs.GT(Computer Science and Game Theory), cs.DB(Databases), cs.DL(Digital Libraries), cs.DM(Discrete Mathematics). Directly output the class name.

gpt: cs.CR(Cryptography and Security)